public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/40435] [4.5 regression] Many regressions on trunk Date: Tue, 16 Jun 2009 02:28:00 -0000 [thread overview] Message-ID: <20090616022825.13063.qmail@sourceware.org> (raw) In-Reply-To: <bug-40435-682@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from hp at gcc dot gnu dot org 2009-06-16 02:28 ------- Mee too! I mean, seen for cris-elf too! BTW, isn't it odd that for recent regressions, the committer's testing never seem to have shown the regressions seen by "every other target" after commit? 1/2 ;) (Definitely _not_ just you, Aldy.) -- hp at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hp at gcc dot gnu dot org Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2009-06-16 02:28:24 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40435
next prev parent reply other threads:[~2009-06-16 2:28 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-06-13 20:20 [Bug c/40435] New: " hjl dot tools at gmail dot com 2009-06-13 20:22 ` [Bug c/40435] " hjl dot tools at gmail dot com 2009-06-13 20:28 ` hjl dot tools at gmail dot com 2009-06-13 21:28 ` aldyh at gcc dot gnu dot org 2009-06-16 2:28 ` hp at gcc dot gnu dot org [this message] 2009-06-16 2:36 ` hp at gcc dot gnu dot org 2009-06-16 4:31 ` [Bug c/40435] [4.5 regression] Revision 148442 caused many " hjl dot tools at gmail dot com 2009-06-17 13:00 ` aldyh at gcc dot gnu dot org 2009-06-17 15:02 ` jsm28 at gcc dot gnu dot org 2009-07-09 12:32 ` aldyh at gcc dot gnu dot org 2009-07-09 15:39 ` rguenth at gcc dot gnu dot org 2009-07-16 22:30 ` manu at gcc dot gnu dot org 2009-07-16 22:38 ` manu at gcc dot gnu dot 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=20090616022825.13063.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).