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 middle-end/45722] [4.6 Regression] FAIL: gcc.c-torture/execute/20040709-2.c execution at -O1 and -Os
Date: Thu, 04 Nov 2010 11:21:00 -0000	[thread overview]
Message-ID: <bug-45722-4-18tV57Agwv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45722-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45722

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #19 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-11-04 11:20:51 UTC ---
I assume this has been fixed (and thus is a dup of PR45678).  I can't see
the FAIL in recent testresult postings for hppa-linux.


  parent reply	other threads:[~2010-11-04 11:21 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45722-4@http.gcc.gnu.org/bugzilla/>
2010-09-29 20:07 ` rguenth at gcc dot gnu.org
2010-10-09 20:47 ` dave at hiauly1 dot hia.nrc.ca
2010-10-09 20:47 ` dave at hiauly1 dot hia.nrc.ca
2010-10-09 21:05 ` danglin at gcc dot gnu.org
2010-10-09 21:27 ` danglin at gcc dot gnu.org
2010-10-11 14:33 ` danglin at gcc dot gnu.org
2010-10-11 16:30 ` danglin at gcc dot gnu.org
2010-10-11 18:08 ` danglin at gcc dot gnu.org
2010-10-11 19:09 ` danglin at gcc dot gnu.org
2010-10-11 21:17 ` dave at hiauly1 dot hia.nrc.ca
2010-10-28 17:50 ` ro at gcc dot gnu.org
2010-11-04 11:21 ` rguenth at gcc dot gnu.org [this message]
2010-11-04 20:24 ` ro at gcc dot gnu.org
2010-11-11 11:44 ` rguenth at gcc dot gnu.org
2010-11-11 21:45 ` ro at CeBiTec dot Uni-Bielefeld.DE
2010-11-11 21:48 ` ro at gcc dot gnu.org
2010-11-11 21:49 ` ro at gcc dot gnu.org
2010-11-12 10:12 ` ebotcazou at gcc dot gnu.org
2010-11-12 10:51 ` ebotcazou at gcc dot gnu.org
2010-11-12 10:52 ` ebotcazou at gcc dot gnu.org
2010-11-12 11:41 ` ebotcazou at gcc dot gnu.org
2010-11-12 12:37 ` rguenth at gcc dot gnu.org
2010-11-12 13:04 ` rguenth at gcc dot gnu.org
2010-11-12 13:13 ` rguenth at gcc dot gnu.org
2010-11-12 13:17 ` rguenth at gcc dot gnu.org
2010-11-12 17:44 ` ebotcazou at gcc dot gnu.org
2010-11-12 17:45 ` ebotcazou at gcc dot gnu.org
2010-11-14 11:36 ` [Bug tree-optimization/45722] " ebotcazou at gcc dot gnu.org
2010-11-14 11:41 ` ebotcazou at gcc dot gnu.org
2010-11-22 17:06 ` ro at CeBiTec dot Uni-Bielefeld.DE
2010-11-23 23:58 ` [Bug middle-end/45722] " danglin at gcc dot gnu.org
2010-11-24  8:50 ` [Bug tree-optimization/45722] " ebotcazou at gcc dot gnu.org
2010-09-18 18:31 [Bug middle-end/45722] New: " danglin at gcc dot gnu dot org
2010-09-18 18:43 ` [Bug middle-end/45722] [4.6 Regression] " rguenth at gcc dot gnu dot org
2010-09-18 19:40 ` dave at hiauly1 dot hia dot nrc dot ca
2010-09-19 20:09 ` dave at hiauly1 dot hia dot nrc dot ca

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-45722-4-18tV57Agwv@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: 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).