[M3devel] tracing implementation minutae -- parity with automatic tracing of mangled names?
Jay K
jay.krell at cornell.edu
Mon Sep 13 09:18:12 CEST 2010
wherever we have:
static void
m3cg_import_global (void)
{
NAME (name, name_length);
...
TYPEID (id);
...
DECL_NAME (v) = fix_name (name, name_length, id);
if (option_trace_all)
fprintf (stderr, " ...%s...", .. POINTER (DECL_NAME (v)));
The "automatic tracing" can't achieve parity.
I see three choices:
- don't achieve parity -- don't print the m3 mangled name
- leave in some manual tracing
- move the TYPEID parameters to right after the NAME parameters,
and then introduce a new macro M3NAME that reads them in succession
and traces them with parity
The last works, but touches, well, not necessarily the m3cg interface and all the implementations, etc.,
but at least the binary writer/reader. Seems a bit expensive..but maybe not.
- Jay
More information about the M3devel
mailing list