This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/12293] wrong mangled names for some "global constructors keyed to"
- From: "carlo at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Sep 2003 20:09:23 -0000
- Subject: [Bug c++/12293] wrong mangled names for some "global constructors keyed to"
- References: <20030916001510.12293.carlo@alinoe.com>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12293
carlo at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From carlo at gcc dot gnu dot org 2003-09-30 20:09 -------
I looked at the source code that generates these symbols,
and apparently it IS on purpose. I am still not convinced
that a disambiguation part is needed here because I under-
stand there is at most one _GLOBAL__I_ symbol per compilation
unit, but well - it is used, so instead I'll fix the demangler
to understand it.
The format of _GLOBAL__I_* symbols is apparently:
_GLOBAL__I_<first global symbol in compilation unit>
or if that doesn't exist
_GLOBAL__I_<first weak global symbol in compilation unit><disambiguation part>
or, if there is no weak symbol either
_GLOBAL__I_<disambiguation part>