public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/65277] [5 Regression] ice in get_untransformed_body with -O2 Date: Mon, 02 Mar 2015 14:43:00 -0000 [thread overview] Message-ID: <bug-65277-4-bb3EvRFrOK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65277-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65277 Kai Tietz <ktietz at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-03-02 CC| |ktietz at gcc dot gnu.org, | |maxim at trivialbugs dot com Ever confirmed|0 |1 --- Comment #1 from Kai Tietz <ktietz at gcc dot gnu.org> --- Issue seems to be happend in expand_all_functions. In prior versions we called expand_function, but now we are calling directly expand (). Expand () itself makes use of function get_untransformed_body, which checks for in-LTO-mode, which of course fails. Anyway the most funny thing here is that this change is not mentioned in any ChangeLog. It is caused by r214422
next prev parent reply other threads:[~2015-03-02 14:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-02 13:52 [Bug c++/65277] New: " dcb314 at hotmail dot com 2015-03-02 14:02 ` [Bug c++/65277] [5 Regression] " rguenth at gcc dot gnu.org 2015-03-02 14:43 ` ktietz at gcc dot gnu.org [this message] 2015-03-02 15:24 ` mpolacek at gcc dot gnu.org 2015-03-02 15:58 ` ktietz at gcc dot gnu.org 2015-03-02 23:29 ` hubicka at gcc dot gnu.org 2015-03-03 13:07 ` [Bug ipa/65277] " marxin 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-65277-4-bb3EvRFrOK@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).