This is the mail archive of the
mailing list for the GCC project.
Re: [RFC] Dealing with ODR violations in GCC
- From: Jan Hubicka <hubicka at ucw dot cz>
- To: Jason Merrill <jason at redhat dot com>
- Cc: Jan Hubicka <hubicka at ucw dot cz>, Martin Liška <mliska at suse dot cz>, gcc at gcc dot gnu dot org
- Date: Tue, 17 Feb 2015 04:49:44 +0100
- Subject: Re: [RFC] Dealing with ODR violations in GCC
- Authentication-results: sourceware.org; auth=none
- References: <20140912054042 dot GB10910 at kam dot mff dot cuni dot cz> <54B66FB9 dot 8050607 at suse dot cz> <20150115054758 dot GB11672 at atrey dot karlin dot mff dot cuni dot cz> <54DE4857 dot 3090601 at suse dot cz> <20150217002703 dot GA25266 at atrey dot karlin dot mff dot cuni dot cz> <54E2AFA4 dot 7000507 at redhat dot com>
> On 02/16/2015 07:27 PM, Jan Hubicka wrote:
> >Jason, I wonder if there is more informative way to print destructor during LTO than as __comp_dtor?
> You could print the mangled name, and possibly run it through
> __cxa_demangle if it starts with _Z.
> >Laos for named types,
> >perhaps printing just type name instead of the wrong "struct typename" (because we make no difference between struct and
> >class at LTO) would be cleaner.
> That makes sense.
Since we have mangled names for types, too, I think it is matter of convincing the LTO langhooks doing the right
thing and using demanlger... I will try to look into this.