Files
mercury/deep_profiler
Julien Fischer f36510b22e Make stage 1 C# executables work with Mono.
They do not currently work in-situ because the launcher scripts we generate do
not set MONO_PATH appropriately. Use the new --mono-path-directory option to
remedy this.

compiler/COMP_FLAGS.in:
deep_profiler/DEEP_FLAGS.in:
grade_lib/GRADE_LIB_FLAGS.in:
mfilterjava/MFILTERJAVAC_FLAGS.in:
profiler/PROF_FLAGS.in:
slice/SLICE_FLAGS.in:
    As above.
2025-08-02 15:07:25 +10:00
..
2016-07-18 15:48:33 +10:00
2025-07-31 10:27:56 +02:00
2025-01-24 13:38:10 +11:00
2025-01-24 13:38:10 +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.