public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/55466] [4.8 Regression] Revision 191466 destroyed DWARF debug info Date: Fri, 07 Dec 2012 10:43:00 -0000 [thread overview] Message-ID: <bug-55466-4-igYOpXV5Wx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55466-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55466 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> 2012-12-07 10:42:42 UTC --- Only LTRANS should be affected - WPA definitely does not need any of this (rest_of_decl_compilation). LTRANS OTOH does not need any type / symtab merging. Merged WPA/LTRANS phase of course complicates things here. What I can't see is why this all should make a difference at LTRANS? Do we garbage-collect unused globals there before wrapping up global decls? Do we somehow not ship them to the correct LTRANS units? We'd wanted to get rid of lto_global_var_decls orginally (replace it by symtab). At the moment it's _only_ used for calling rest_of_decl_compilation on globals (and for static we call that twice ...). So, HJ, your patch does look reasonable for 4.8 - can you give it proper testing and submit it? OTOH the LTO path should not call rest_of_decl_compilation but sth more specific ... (most of it is disabled for the LTO path anyway).
next prev parent reply other threads:[~2012-12-07 10:43 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-25 22:47 [Bug lto/55466] New: " hjl.tools at gmail dot com 2012-11-26 12:45 ` [Bug lto/55466] " hubicka at ucw dot cz 2012-11-26 15:57 ` rguenth at gcc dot gnu.org 2012-11-26 15:58 ` rguenth at gcc dot gnu.org 2012-11-26 16:36 ` hjl.tools at gmail dot com 2012-11-28 21:26 ` hjl.tools at gmail dot com 2012-11-29 18:53 ` hubicka at gcc dot gnu.org 2012-11-29 19:08 ` hjl.tools at gmail dot com 2012-11-29 19:09 ` hjl.tools at gmail dot com 2012-12-07 10:43 ` rguenth at gcc dot gnu.org [this message] 2012-12-07 13:02 ` hjl.tools at gmail dot com 2012-12-07 18:49 ` hjl.tools at gmail dot com 2012-12-10 14:44 ` hjl at gcc dot gnu.org 2012-12-10 16:40 ` hjl.tools at gmail dot com 2013-01-03 16:55 ` hjl at gcc dot gnu.org
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-55466-4-igYOpXV5Wx@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).