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/66468] [6 Regression] ICE in in check_die, at dwarf2out.c:5719 Date: Mon, 20 Jul 2015 22:14:00 -0000 [thread overview] Message-ID: <bug-66468-4-Ppz435Ppkv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66468-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66468 --- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> --- The problem seems to be that we inlined the function, but DECL_POSSIBLY_INLINED remains unset, so dwarf2out doesn't think it needs to call dwarf2out_abstract_function. There also doesn't seem to be a cgraph edge for the inlined function call; I'm guessing that the function was inlined in the initial compilation, and this relationship is forgotten by the time we get to LTO. So, doesn't look like a dwarf2out bug.
next prev parent reply other threads:[~2015-07-20 22:14 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-66468-4@http.gcc.gnu.org/bugzilla/> 2015-06-09 8:52 ` trippels at gcc dot gnu.org 2015-06-09 9:12 ` rguenth at gcc dot gnu.org 2015-06-09 14:38 ` aldyh at gcc dot gnu.org 2015-07-17 20:10 ` hjl.tools at gmail dot com 2015-07-20 18:22 ` jason at gcc dot gnu.org 2015-07-20 22:14 ` jason at gcc dot gnu.org [this message] 2015-07-21 17:10 ` jason at gcc dot gnu.org 2015-07-21 18:12 ` jason at gcc dot gnu.org 2015-07-27 16:57 ` jason at gcc dot gnu.org 2015-07-27 17:00 ` [Bug lto/66468] " jason at gcc dot gnu.org 2015-08-06 2:28 ` miyuki at gcc dot gnu.org 2015-08-15 7:59 ` trippels at gcc dot gnu.org 2015-09-03 9:56 ` rguenth at gcc dot gnu.org 2015-09-03 10:00 ` rguenth 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-66468-4-Ppz435Ppkv@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).