public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/35388] [4.2 Regression] error compiling dealII SPEC CPU 2006 benchmark Date: Tue, 31 Mar 2009 15:18:00 -0000 [thread overview] Message-ID: <20090331151800.11417.qmail@sourceware.org> (raw) In-Reply-To: <bug-35388-15836@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from jsm28 at gcc dot gnu dot org 2009-03-31 15:18 ------- No response from submitter in > 1 year, closing. -- jsm28 at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |INVALID Target Milestone|4.2.5 |--- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35388
prev parent reply other threads:[~2009-03-31 15:18 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-27 10:23 [Bug c++/35388] New: [Alpha OSF V5.1] " dario at unizar dot es 2008-02-27 10:24 ` [Bug c++/35388] " dario at unizar dot es 2008-02-27 10:25 ` dario at unizar dot es 2008-03-24 16:24 ` [Bug rtl-optimization/35388] [4.2 Regression] " falk at debian dot org 2008-03-27 22:25 ` rguenth at gcc dot gnu dot org 2008-05-19 20:34 ` jsm28 at gcc dot gnu dot org 2009-03-31 15:18 ` jsm28 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=20090331151800.11417.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).