[m-dev.] Performance of collect

[Erwan Jahier]

| On 25-Sep-2000, Erwan Jahier <Erwan.Jahier at irisa.fr> wrote:
| > | On 24-Sep-2000, Erwan Jahier <Erwan.Jahier at irisa.fr> wrote:
| > | > | You're calling from C to Mercury.  In our current implementation (LLDS back-end),
| > | > | this is fairly expensive.  
| > | > 
| > | > So what about the HLDS back-end then?
| > | > 
| > | > Is it ready to use?
| > | 
| > | Yes, but not for tracing -- currently it doesn't support the debugger.
| > 
| > Well currently, you can not use the debugger to debug collect programs anyway
| > (it is dynamically linked code). So ...
| 
| Currently the MLDS back-end doesn't generate *any* calls to MR_trace().
| So it can't be used for any kind of tracing, whether it be mdb, Morphine,
| the declarative debugger, or collect.

Yes, I have understood that. My idea was to use the LLDS back-end (or whatever
back-end) to compile the Mercury program to be monitored, and to use the MLDS
back-end to compile the monitor (the collect module).

Currently, it seems to be impossible to mix code that have been compiled in
different grades; what are the reasons for that? Do those reasons still hold for
the MLDS back-end?

-- 
R1.


--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------