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 tree-optimization/64495] [4.8/4.9/5 Regression] ICE at -O3 for trunk and wrong code for 4.8/4.9 on x86_64-linux-gnu
Date: Mon, 05 Jan 2015 08:54:00 -0000 [thread overview]
Message-ID: <bug-64495-4-oWlEAyitpv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64495-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64495
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-01-05
CC| |mpolacek at gcc dot gnu.org
Target Milestone|--- |4.8.5
Summary|ICE at -O3 for trunk and |[4.8/4.9/5 Regression] ICE
|wrong code for 4.8/4.9 on |at -O3 for trunk and wrong
|x86_64-linux-gnu |code for 4.8/4.9 on
| |x86_64-linux-gnu
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed. I get an ICE with this testcase even with 4.8/4.9 (with checking
enabled).
next parent reply other threads:[~2015-01-05 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-64495-4@http.gcc.gnu.org/bugzilla/>
2015-01-05 8:54 ` mpolacek at gcc dot gnu.org [this message]
2015-01-05 9:00 ` jakub at gcc dot gnu.org
2015-01-13 12:30 ` rguenth at gcc dot gnu.org
2015-01-14 8:33 ` rguenth at gcc dot gnu.org
2015-01-14 8:34 ` [Bug tree-optimization/64495] [4.8/4.9 " rguenth at gcc dot gnu.org
2015-02-19 14:14 ` rguenth at gcc dot gnu.org
2015-02-24 14:26 ` [Bug tree-optimization/64495] [4.8 " rguenth at gcc dot gnu.org
2015-02-24 14:27 ` 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-64495-4-oWlEAyitpv@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: link
Be 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).