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 regression/19829] [4.0 regression] cris-elf testsuite failure: 21_strings/basic_string/find/char/3.cc execution test
Date: Tue, 15 Feb 2005 05:36:00 -0000	[thread overview]
Message-ID: <20050214222559.22522.qmail@sourceware.org> (raw)
In-Reply-To: <20050208194601.19829.hp@gcc.gnu.org>


------- Additional Comments From hp at gcc dot gnu dot org  2005-02-14 22:25 -------
I'm reopening this bug as I see the regression with LAST_UPDATED
"Mon Feb 14 15:49:50 UTC 2005" (on a stable machine this time)
where I did not see it with "Mon Feb 14 07:18:25 UTC 2005".

Keeping this PR open until it's properly analyzed, noting the success
and failure LAST_UPDATED and any change in log contents
(same as first time, at reopen).


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


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


  parent reply	other threads:[~2005-02-14 22:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09  6:38 [Bug regression/19829] New: " hp at gcc dot gnu dot org
2005-02-10 13:18 ` [Bug regression/19829] " hp at gcc dot gnu dot org
2005-02-10 13:21 ` hp at gcc dot gnu dot org
2005-02-15  5:36 ` hp at gcc dot gnu dot org [this message]
2005-02-16 14:14 ` hp at gcc dot gnu dot org
2005-02-16 14:15 ` pinskia at gcc dot gnu dot org
2005-02-16 16:20 ` pcarlini at suse dot de
2005-02-16 16:23 ` [Bug libstdc++/19829] " cvs-commit at gcc dot gnu dot org
2005-02-16 16:28 ` cvs-commit at gcc dot gnu dot org
2005-02-16 16:30 ` pcarlini at suse dot de

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=20050214222559.22522.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).