[m-rev.] for review: add a demangled name field to MR_ProcIds

[Zoltan Somogyi]

On 02-Jan-2002, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > At the moment, the browser library is linked into executables iff they are
> > compiled with debugging. The mangle/demangle module would need to be linked
> > into several programs (compiler, the profilers, mdemangle) regardless of
> > whether they are compiled with debugging.
> 
> The browser library is currently always linked into the compiler and the
> profilers, regardless of whether they are compiled with debugging information.
> 
> This is a waste of code space, I guess, so your suggestion below ...

Actually, we were both wrong. You were wrong because there is no waste of code
space. The browser library is always specified on the command line, but
without debugging, nothing from it is linked into the profilers, since it
doesn't define any symbols they leave unresolved. I was wrong because the
compiler does explicitly refer to browser/program_representation.m, and so
its object file (but not the rest of the browser library) is always linked
into the compiler.

Given that there is no other good place to put program_representation.m, we may
as well put the name mangling code may into the browser directory after all.

Zoltan.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------