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/55964] [4.7 Regression] Segmentation fault with -O -ftree-loop-distribution -funswitch-loops Date: Wed, 03 Apr 2013 09:48:00 -0000 [thread overview] Message-ID: <bug-55964-4-hJhwEWzDGJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55964-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55964 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ice-on-valid-code Priority|P3 |P2 Known to work| |4.8.0 Known to fail| |4.7.2 --- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> 2013-04-03 09:48:00 UTC --- Backport unlikely.
next prev parent reply other threads:[~2013-04-03 9:48 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-13 19:26 [Bug tree-optimization/55964] New: " antoine.balestrat at gmail dot com 2013-01-14 12:34 ` [Bug tree-optimization/55964] [4.7/4.8 Regression] " jakub at gcc dot gnu.org 2013-01-14 13:15 ` rguenth at gcc dot gnu.org 2013-01-16 14:07 ` rguenth at gcc dot gnu.org 2013-01-16 14:23 ` [Bug tree-optimization/55964] [4.7 " jakub at gcc dot gnu.org 2013-04-03 9:48 ` rguenth at gcc dot gnu.org [this message] 2013-04-03 9:50 ` rguenth at gcc dot gnu.org 2013-04-03 10:38 ` rguenth at gcc dot gnu.org 2013-04-08 11:08 ` rguenth at gcc dot gnu.org 2013-04-11 8:01 ` rguenth at gcc dot gnu.org 2014-05-06 12:03 ` rguenth at gcc dot gnu.org 2014-06-12 13:21 ` 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-55964-4-hJhwEWzDGJ@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).