public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/48148] [4.7 Regression] bootstrap failed with bootstrap-profiled Date: Wed, 16 Mar 2011 17:04:00 -0000 [thread overview] Message-ID: <bug-48148-4-MlLn9ZTNio@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48148-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48148 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|jakub at redhat dot com |jan.kratochvil at redhat | |dot com --- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> 2011-03-16 17:03:58 UTC --- I believe it is a LTO speciality, I can't imagine how non-lto would end up with DECL_EXTERNAL with DECL_ABSTRACT_ORIGIN set, so I guess your patch is an alternative. Or: --- dwarf2out.c.jj 2011-03-16 09:37:40.000000000 +0100 +++ dwarf2out.c 2011-03-16 17:28:36.054796163 +0100 @@ -22927,7 +22927,9 @@ resolve_addr (dw_die_ref die) { tree tdecl = SYMBOL_REF_DECL (a->dw_attr_val.v.val_addr); dw_die_ref tdie = lookup_decl_die (tdecl); - if (tdie == NULL && DECL_EXTERNAL (tdecl)) + if (tdie == NULL + && DECL_EXTERNAL (tdecl) + && DECL_ABSTRACT_ORIGIN (tdecl) == NULL_TREE) { force_decl_die (tdecl); tdie = lookup_decl_die (tdecl); that I'm testing right now. DW_TAG_GNU_call_site won't be very useful in that case anyway, because if the extern is "read_string.constprop.0" with that DW_AT_name, I bet the debugger won't be able to match it to the definition DIE anyway. I think currently for read_string.constprop.0 in the definition CU we will just have DW_TAG_subprogram DW_AT_abstract_origin <read_string DIE> and not any DW_AT_name (which is thought to be the same as abstract origin's name, correct for the clones) and no DW_AT_linkage_name (guess it would be desirable to provide a linkage name if the clone has a different name from the origin).
next prev parent reply other threads:[~2011-03-16 17:04 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-16 12:52 [Bug bootstrap/48148] New: [4.7 Regression] LTO " hjl.tools at gmail dot com 2011-03-16 12:54 ` [Bug bootstrap/48148] " hjl.tools at gmail dot com 2011-03-16 12:59 ` hjl.tools at gmail dot com 2011-03-16 13:38 ` jakub at gcc dot gnu.org 2011-03-16 14:51 ` hjl.tools at gmail dot com 2011-03-16 15:32 ` [Bug bootstrap/48148] [4.7 Regression] " hjl.tools at gmail dot com 2011-03-16 15:36 ` jakub at gcc dot gnu.org 2011-03-16 16:21 ` jakub at gcc dot gnu.org 2011-03-16 16:30 ` rguenth at gcc dot gnu.org 2011-03-16 16:30 ` rguenth at gcc dot gnu.org 2011-03-16 17:04 ` jakub at gcc dot gnu.org [this message] 2011-03-16 17:56 ` jan.kratochvil at redhat dot com 2011-03-16 18:01 ` jakub at gcc dot gnu.org 2011-03-16 18:05 ` jan.kratochvil at redhat dot com 2011-03-17 13:26 ` rguenth at gcc dot gnu.org 2011-03-17 13:28 ` rguenth at gcc dot gnu.org 2011-03-17 13:32 ` hjl.tools at gmail dot com 2011-03-17 13:35 ` jakub at gcc dot gnu.org 2011-03-17 14:41 ` hjl.tools at gmail dot com 2011-03-17 17:22 ` [Bug bootstrap/48148] [4.7 Regression] LTO " hjl.tools at gmail dot com 2011-03-17 20:34 ` jakub at gcc dot gnu.org 2011-03-24 7:58 ` hjl.tools at gmail dot com 2011-03-31 15:02 ` hjl.tools at gmail dot com 2011-04-01 21:14 ` jakub at gcc dot gnu.org 2011-04-04 19:24 ` hjl.tools at gmail dot com 2011-04-04 20:01 ` hjl.tools at gmail dot com 2011-04-05 2:52 ` hjl.tools at gmail dot com 2011-04-19 14:46 ` ebotcazou at gcc dot gnu.org 2011-04-19 14:49 ` ebotcazou at gcc dot gnu.org 2011-04-20 11:21 ` ebotcazou 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-48148-4-MlLn9ZTNio@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).