This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] Dealing with ODR violations in GCC


> 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.

Honza
> 
> Jason
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]