Files
mercury/deep_profiler
Zoltan Somogyi baddfd37cd Make --warn-unused-imports the default for the Mercury system.
browser/MDB_FLAGS.in:
compiler/COMP_FLAGS.in:
deep_profiler/DEEP_FLAGS.in:
library/LIB_FLAGS.in:
mdbcomp/MDBCOMP_FLAGS.in:
mfilterjavac/MFILTERJAVAC_FLAGS.in:
profiler/PROF_FLAGS.in:
slice/SLICE_FLAGS.in:
ssdb/SSDB_FLAGS.in:
    Add --warn-unused-imports to the list of default compiler flags
    for each directory.

compiler/ml_tailcall.m:
library/io.m:
    Delete some unused imports.
2017-01-19 10:48:04 +11:00
..
2016-07-18 15:48:33 +10:00
2016-05-25 15:42:53 +10:00
2016-01-23 14:03:37 +11:00
2016-04-25 20:03:09 +10:00
2016-01-23 14:03:37 +11:00

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.