public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/65655] [5 Regression] ICE in speculative_call_info, at cgraph.c:1151 Date: Wed, 01 Apr 2015 17:16:00 -0000 [thread overview] Message-ID: <bug-65655-4-6l5mHe2xJu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65655-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65655 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|ice-on-invalid-code |ice-on-valid-code Component|sanitizer |ipa Summary|[5 Regression][UBSAN] ICE |[5 Regression] ICE in |in speculative_call_info, |speculative_call_info, at |at cgraph.c:1151 |cgraph.c:1151 --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- But it ICEs even without -fsanitize=undefined, so likely an IPA issue. Also I don't see what's invalid in this testcase, it compiles OK with -O.
next prev parent reply other threads:[~2015-04-01 17:16 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-01 17:05 [Bug sanitizer/65655] New: [5 Regression][UBSAN] " burnus at gcc dot gnu.org 2015-04-01 17:14 ` [Bug sanitizer/65655] " mpolacek at gcc dot gnu.org 2015-04-01 17:16 ` mpolacek at gcc dot gnu.org [this message] 2015-04-01 18:28 ` [Bug ipa/65655] [5 Regression] " mpolacek at gcc dot gnu.org 2015-04-02 8:47 ` rguenth at gcc dot gnu.org 2015-04-02 16:21 ` hubicka at gcc dot gnu.org 2015-04-03 0:23 ` hubicka at gcc dot gnu.org 2015-04-03 18:20 ` hubicka at gcc dot gnu.org 2015-04-03 18:21 ` hubicka 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-65655-4-6l5mHe2xJu@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).