This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [C++] Avoid one place of frontend calling into targetm
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- To: sje at cup dot hp dot com (Steve Ellcey)
- Cc: jh at suse dot cz, gcc-patches at gcc dot gnu dot org
- Date: Mon, 4 Jun 2007 15:07:38 -0400 (EDT)
- Subject: Re: [C++] Avoid one place of frontend calling into targetm
> OK, In the mean time here is a bit more information, I think this is the
> same as PR 31908 and may be related to PR 30151. I just noticed while
> looking around some more that while _GLOBAL__I_c went from being global
> to being static, there is a new global variable called _GLOBAL__I_0_c
> that wasn't there before. _GLOBAL__I_0_c has a call to _GLOBAL__I_c, so
> it looks like the bug is that the call from the code created by collect2
> is using the static name, _GLOBAL__I_c, instead of the global name,
> _GLOBAL__I_0_c.
It's probably trying to setup calls to both. Don't think static variables
should start with "_GLOBAL__".
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)