This is the mail archive of the
mailing list for the GCC project.
Re: LTO inhibiting dwarf lexical blocks output
- From: Richard Biener <richard dot guenther at gmail dot com>
- To: Aldy Hernandez <aldyh at redhat dot com>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Tue, 19 Aug 2014 10:22:28 +0200
- Subject: Re: LTO inhibiting dwarf lexical blocks output
- Authentication-results: sourceware.org; auth=none
- References: <53EE66B1 dot 7040105 at redhat dot com> <CAFiYyc0LUx1XQ8FJ8CMxhCP_DwNqQP3fVeAbxLB2NNts9bU_=g at mail dot gmail dot com> <CAFiYyc1JLabNVGhXZC10+U8gbgAAmk9i_4C29KX_sp3moeWy-w at mail dot gmail dot com> <53F26FA1 dot 1060200 at redhat dot com>
On Mon, Aug 18, 2014 at 11:26 PM, Aldy Hernandez <email@example.com> wrote:
> On 08/18/14 07:31, Richard Biener wrote:
>> On Mon, Aug 18, 2014 at 12:46 PM, Richard Biener
>> <firstname.lastname@example.org> wrote:
>>> On Fri, Aug 15, 2014 at 9:59 PM, Aldy Hernandez <email@example.com> wrote:
>>> For the rest them on the floor instead of ICEing in dwarf2out.c.
> Should that read "For the rest, drop them on the floor..."???
Yes. Btw, debugging works quite well with LTO and C(-like) source,
it's only when you start using C++ and its features that it breaks
down completely due to missing langhooks. Like for example
the libstdc++ pretty-printers not working. For example in
free_lang_data_in_type we drop all FUNCTION_DECLs from
TYPE_FIELDS (so you don't have any methods anymore).
Such stuff is also a reason why free-lang-data runs only with -flto,
otherwise we'd break debug info for non-LTO. So clearly the
dwarf for types and decls we apply free_lang_data_in_X to has
to be emitted before we do that.
> I'm having a hard time parsing the above.
>> The following seems to fix it. In testing now.
> Sweet! Thanks a lot!
> And thanks for the explanations.