This is the mail archive of the
mailing list for the GCC project.
Re: [RFC] Dealing with ODR violations in GCC
- From: Jason Merrill <jason at redhat dot com>
- To: Jan Hubicka <hubicka at ucw dot cz>, Martin Liška <mliska at suse dot cz>
- Cc: gcc at gcc dot gnu dot org
- Date: Mon, 16 Feb 2015 22:04:04 -0500
- 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>
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.