This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] Fix PR 51910, -frepo/linker demangling interaction
- From: Jason Merrill <jason at redhat dot com>
- To: Sandra Loosemore <sandra at codesourcery dot com>
- Cc: Jakub Jelinek <jakub at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Wed, 01 Feb 2012 14:31:45 -0500
- Subject: Re: [PATCH] Fix PR 51910, -frepo/linker demangling interaction
- References: <4F25DF6A.firstname.lastname@example.org> <20120130142341.GF18768@tyan-ft48-01.lab.bos.redhat.com> <4F26BA55.email@example.com> <20120130161124.GH18768@tyan-ft48-01.lab.bos.redhat.com> <4F26FCF8.firstname.lastname@example.org> <20120201135629.GR18768@tyan-ft48-01.lab.bos.redhat.com> <4F2989CF.email@example.com>
On 02/01/2012 01:51 PM, Sandra Loosemore wrote:
I don't think this is even really a regression.
The testcase works with 4.6 and not with pre-4.7; that makes it a
I haven't actually sat
down to try to reproduce this, but backing out the previous patch would
leave the -frepo behavior even more broken on Windows hosts than it is
now; one of the bugs fixed by the previous patch was that on Windows
collect2 *always* told ld to demangle names and there was no way for
users to override this via a command-line option or setting
COLLECT_NO_DEMANGLE. And, I think the -frepo bug was present on Linux
hosts too if you explicitly configured your GCC build with
--with-demangler-in-ld, which is what you need to do if you want ld to
be able to produce demangled link maps at all.
(BTW, the CodeSourcery IDE adds -Wl,-Map to the link line by default
because it's easier to always generate a link map than to have to
explain to users how to get one. Especially in the embedded space, it's
something many of our users actually do look at.)
Why do you want the link map to be demangled? It seems more reliable to
deal with mangled symbols; there's always c++filt if you want to check
what the symbols demangle to.