This is the mail archive of the gcc-patches@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: [PATCH] Fix the most annoying LTO -g ICE in dwarf2out.c

From: Jason Merrill <jason at redhat dot com>
To: Richard Guenther <rguenther at suse dot de>
Cc: gcc-patches at gcc dot gnu dot org
Date: Tue, 19 Oct 2010 17:47:50 -0400
Subject: Re: [PATCH] Fix the most annoying LTO -g ICE in dwarf2out.c
References: <alpine.LNX.2.00.1010081602350.8982@zhemvz.fhfr.qr> <4CB376AA.5030104@redhat.com> <alpine.LNX.2.00.1010121036020.8982@zhemvz.fhfr.qr> <alpine.LNX.2.00.1010181754400.23074@zhemvz.fhfr.qr> <4CBCB985.3080605@redhat.com> <alpine.LNX.2.00.1010191110080.23074@zhemvz.fhfr.qr>

On 10/19/2010 05:13 AM, Richard Guenther wrote:

A workaround on the LTO side would be to clear
DECL_CONTEXT on such functions.


On which functions?  How do you detect on the LTO side that type merging has
gone wrong?


On all functions which have a record or union type DECL_CONTEXT
(all functions that are in some TYPE_METHODS which we do not
stream).  Of course I can't detect whether type merging has gone wrong.

That would be overkill, stipping debug info even when the types are ok.

Jason

References:
- [PATCH] Fix the most annoying LTO -g ICE in dwarf2out.c
  - From: Richard Guenther
- Re: [PATCH] Fix the most annoying LTO -g ICE in dwarf2out.c
  - From: Jason Merrill
- Re: [PATCH] Fix the most annoying LTO -g ICE in dwarf2out.c
  - From: Richard Guenther
- Re: [PATCH] Fix the most annoying LTO -g ICE in dwarf2out.c
  - From: Richard Guenther
- Re: [PATCH] Fix the most annoying LTO -g ICE in dwarf2out.c
  - From: Jason Merrill
- Re: [PATCH] Fix the most annoying LTO -g ICE in dwarf2out.c
  - From: Richard Guenther

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