Files
mercury/deep_profiler
Zoltan Somogyi 0c7af82fc6 Use += instead of = to set MCFLAGS-modulename.
*/Mercury.options:
    Specify module-specific Mercury compiler flags using

        MCFLAGS-modulename += options

    instead of

        MCFLAGS-modulename = options

    because unlike the latter, the former allows Mmake.params files
    to add other options.
2023-10-06 00:04:07 +11:00
..
2023-07-01 02:25:53 +10:00
2022-01-09 10:36:15 +11:00
2022-03-17 13:52:46 +11:00
2023-08-15 00:19:34 +02:00
2022-03-04 01:08:55 +11:00
2022-01-09 10:36:15 +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.