[PATCH] Fix outputting of debug info for things marked *INTERNAL* (fwd)

Jason Merrill jason@redhat.com
Sun Feb 18 20:00:00 GMT 2001


>>>>> "Michael" == Michael Elizabeth Chastain <chastain@cygnus.com> writes:

> Jason Merrill writes:
>> I'm not sure what the right representation for stabs is.  Any input?

> Daniel Berlin knows this section of code better than I do.

> My intuition is that gdb ought to be capable of discarding or suppressing
> this information in the demangler.

> Can you clue me in about what the "*INTERNAL*" means in gcc terms?
> Would gdb always want to discard methods marked "*INTERNAL*"?

*INTERNAL* is just an arbitrary string added to the mangled name for the
abstract constructor to distinguish it from the concrete ones.  It
shouldn't make it out of the compiler.

I think that it probably makes sense to suppress the abstract constructor
entirely for non-dwarf debugging backends, since only dwarf has the notion
of instances of an inline function.

I'm wondering if it makes sense to suppress the in-class mention of one of
the concrete constructors as well, so that only one shows up when you do a
ptype.

Jason



More information about the Gcc-patches mailing list