public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39579] [4.5 regression] revisions 145171/145172 caused 2 extra failures
Date: Wed, 22 Apr 2009 13:46:00 -0000 [thread overview]
Message-ID: <20090422134614.531.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39579-682@http.gcc.gnu.org/bugzilla/>
--
rguenth at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39579
next prev parent reply other threads:[~2009-04-22 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 16:49 [Bug middle-end/39579] New: [4.5 regression] Many regressions on trunk hjl dot tools at gmail dot com
2009-03-29 17:04 ` [Bug middle-end/39579] " rguenth at gcc dot gnu dot org
2009-03-29 18:54 ` hjl dot tools at gmail dot com
2009-03-29 18:58 ` hjl dot tools at gmail dot com
2009-04-22 13:46 ` rguenth at gcc dot gnu dot org [this message]
2009-04-30 21:43 ` [Bug middle-end/39579] [4.5 regression] revisions 145171/145172 caused 2 extra failures sje at gcc dot gnu dot org
2009-05-01 14:52 ` sje at cup dot hp dot com
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=20090422134614.531.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: 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).