public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/31642] -O2 -fno-guess-branch-probability -fno-tree-ch -fno-tree-dominator-opts -fno-tree-lrs -fno-tree-dce -fno-tree-vrp -funit-at-a-time -ftree-copy-prop -ftree-copyrename yields an infinite loop in SPEC benchmark 176.gcc Date: Sun, 03 Feb 2008 14:22:00 -0000 [thread overview] Message-ID: <20080203142125.21435.qmail@sourceware.org> (raw) In-Reply-To: <bug-31642-13613@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from steven at gcc dot gnu dot org 2008-02-03 14:21 ------- No test case, no activity, and, really, quite old already. Please re-open if you can still reproduce this. -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31642
prev parent reply other threads:[~2008-02-03 14:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-04-20 14:45 [Bug c/31642] New: " kenneth dot hoste at elis dot ugent dot be 2007-04-20 17:25 ` [Bug middle-end/31642] " pinskia at gcc dot gnu dot org 2007-04-20 18:24 ` [Bug c/31642] " kenneth dot hoste at elis dot ugent dot be 2007-04-20 19:52 ` [Bug middle-end/31642] " kenneth dot hoste at elis dot ugent dot be 2008-02-03 14:22 ` steven at gcc dot gnu dot org [this message]
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=20080203142125.21435.qmail@sourceware.org \ --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).