mirror of
https://github.com/Mercury-Language/mercury.git
synced 2026-04-16 09:53:36 +00:00
41d133b8ad
compiler/check_module_interface.m:
Generate a "this module does not export anything" warning for modules
that contain only single include_module declaration, since such modules
could be deleted with no effect.
Change the warning message to list every kind of declaration/definition
that does not depend on the presence of other kinds of declarations or
definitions.
deep_profiler/Mercury.options:
Shut up this warning for mdprof_fb, since right now, it contains
only a single include_module, even it is designed to later contain more.
tests/invalid/empty_interface.err_exp:
tests/invalid/typeclass_missing_det_3.err_exp:
tests/invalid_nodepend/bigtest.err_exp:
tests/invalid_nodepend/duplicate_modes.err_exp:
tests/invalid_nodepend/errors2.err_exp:
tests/invalid_nodepend/no_exports.err_exp:
tests/invalid_nodepend/prog_io_erroneous.err_exp:
tests/invalid_nodepend/typeclass_test_11.err_exp:
tests/invalid_nodepend/vars_in_wrong_places.err_exp:
Expect the updated wording of the warning message.
For documentation on the deep profiler, see the following:
- The "Deep Profiler" section of the Mercury web page
<http://www.cs.mu.oz.au/mercury/information/deep_demo.html>
gives an overview of what deep profiling is.
- The deep profiling paper on our web site, "Deep profiling:
engineering a profiler for a declarative programming language"
<http://www.cs.mu.oz.au/mercury/information/papers.html#mu_01_24>
explains in detail what deep profiling is, why it is needed,
and how it is implemented in the Mercury compiler.
- The "Using mdprof" section of the "Profiling" chapter of the
Mercury user's guide explains how to use it.
- The file deep_profiler/notes/deep_profiling.html gives an overview of
the specifics details of our implementation of deep profiling.