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 tree-optimization/45957] [4.6 Regression] g++.dg/ext/fnname3.C FAILs with -flto/-fwhopr Date: Thu, 14 Oct 2010 15:14:00 -0000 [thread overview] Message-ID: <20101014151400.g7QNs5SCE9qNgR-dMDQetmLE3UIuYlr9co9Vp1IP52M@z> (raw) In-Reply-To: <bug-45957-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45957 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2010.10.14 15:14:34 AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org |gnu.org | Ever Confirmed|0 |1 --- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-10-14 15:14:34 UTC --- This happens because we clear DECL_INITIAL in free-lang-data and appearantly S::S which is the context of __func__ is DECL_ABSTRACT ... Surely an artifact of the C++ constructor/destructor cloning. We could simply remove if (TREE_CODE (decl) == VAR_DECL) { tree context = DECL_CONTEXT (decl); if (context) { enum tree_code code = TREE_CODE (context); if (code == FUNCTION_DECL && DECL_ABSTRACT (context)) { /* Do not clear the decl context here, that will promote all vars to global ones. */ DECL_INITIAL (decl) = NULL_TREE; } } } from free-lang-data.
next prev parent reply other threads:[~2010-10-14 15:14 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-10-09 21:59 [Bug tree-optimization/45957] New: " zsojka at seznam dot cz 2010-10-09 22:17 ` [Bug tree-optimization/45957] " zsojka at seznam dot cz 2010-10-09 23:21 ` rguenth at gcc dot gnu.org 2010-10-14 15:14 ` rguenth at gcc dot gnu.org [this message] 2010-10-15 10:56 ` rguenth at gcc dot gnu.org 2010-10-15 10:58 ` 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=20101014151400.g7QNs5SCE9qNgR-dMDQetmLE3UIuYlr9co9Vp1IP52M@z \ --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).