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/64495] [4.8/4.9 Regression] ICE at -O3 for trunk and wrong code for 4.8/4.9 on x86_64-linux-gnu Date: Wed, 14 Jan 2015 08:34:00 -0000 [thread overview] Message-ID: <bug-64495-4-9fSaiwleHw@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-checking, | |ice-on-valid-code, | |wrong-code Known to work| |5.0 Summary|[4.8/4.9/5 Regression] ICE |[4.8/4.9 Regression] ICE at |at -O3 for trunk and wrong |-O3 for trunk and wrong |code for 4.8/4.9 on |code for 4.8/4.9 on |x86_64-linux-gnu |x86_64-linux-gnu --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Fixed on trunk sofar.
next prev parent reply other threads:[~2015-01-14 8:34 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 ` [Bug tree-optimization/64495] [4.8/4.9/5 " mpolacek at gcc dot gnu.org 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 ` rguenth at gcc dot gnu.org [this message] 2015-02-19 14:14 ` [Bug tree-optimization/64495] [4.8/4.9 " 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-9fSaiwleHw@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).