public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/53470] [4.8 Regression] ICE when linking with -g in splice_child_die, at dwarf2out.c:4264 Date: Wed, 06 Jun 2012 15:27:00 -0000 [thread overview] Message-ID: <bug-53470-4-w2F2A0NZrI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53470-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53470 --- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> 2012-06-06 15:27:02 UTC --- (In reply to comment #8) > All of the clearing is done to push down memory usage and/or cause > types to be referenced that are otherwise unused. A way to retain the > latter would be to not recurse into TYPE_CONTEXT during find_decls_types_r > and in free_lang_data_in_type only reset TYPE_CONTEXT when > that is not in fld.pset (thus we didn't visit it, aka, it is unused). If a type is nested inside another type, using the inner type necessarily uses the outer type; we need to at least declare the outer type so we have some place to put the inner type. So I don't think there's any optimization opportunity here. > Note that the fundamental issue with running free-lang-data with -g0 > and lto1 with -g is that free-lang-data with -g0 assumes we won't > generate debug information. Yes, but that isn't the problem with this PR; in this case cc1plus and lto1 are both run with -g. free_lang_data_in_type is clearing TYPE_CONTEXT even though we want full debug information, and this lying to the debugging back end results in the ICE.
next prev parent reply other threads:[~2012-06-06 15:27 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-24 9:43 [Bug lto/53470] New: [4.8 LTO] " vincenzo.innocente at cern dot ch 2012-05-24 9:55 ` [Bug lto/53470] " rguenth at gcc dot gnu.org 2012-05-24 17:24 ` hjl.tools at gmail dot com 2012-05-25 7:52 ` vincenzo.innocente at cern dot ch 2012-05-25 8:37 ` markus at trippelsdorf dot de 2012-05-25 12:37 ` [Bug debug/53470] [4.8 Regression] " hjl.tools at gmail dot com 2012-05-29 10:46 ` rguenth at gcc dot gnu.org 2012-06-05 18:07 ` jason at gcc dot gnu.org 2012-06-06 11:56 ` rguenther at suse dot de 2012-06-06 15:27 ` jason at gcc dot gnu.org [this message] 2012-06-06 16:11 ` jason at gcc dot gnu.org 2012-06-11 12:38 ` rguenth at gcc dot gnu.org 2012-06-11 12:55 ` rguenth at gcc dot gnu.org 2012-06-11 13:37 ` jason at gcc dot gnu.org 2012-06-11 14:14 ` rguenth at gcc dot gnu.org 2012-06-11 14:16 ` rguenth at gcc dot gnu.org 2012-06-12 5:17 ` vincenzo.innocente at cern dot ch 2013-02-19 20:38 ` LpSolit at netscape dot net
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-53470-4-w2F2A0NZrI@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).