public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "potswa at mac dot com" <gcc-bugzilla-noreply@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/45841] [4.6 Regression]: r164529 cris-elf libstdc++ 27_io/basic_filebuf/seekoff/char/2-io.cc
Date: Tue, 05 Oct 2010 23:31:00 -0000	[thread overview]
Message-ID: <20101005233100.r2uZ3wdGpu2RTEZzIIcdwi7_PM3U4sjls5de4zY12Vk@z> (raw)
In-Reply-To: <bug-45841-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #37 from David Krauss <potswa at mac dot com> 2010-10-05 23:31:34 UTC ---
(In reply to comment #35)
> Yes and no.  By fixing one of the two (known :) simulator bugs and running the
> test-suite for r164529, the result of that test regressed from PASS to FAIL.

Is it ever a regression (using the proper sense of the word ;v) ) vs my patch?


  parent reply	other threads:[~2010-10-05 23:31 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30 10:14 [Bug libstdc++/45841] New: " hp at gcc dot gnu.org
2010-09-30 10:24 ` [Bug libstdc++/45841] " potswa at mac dot com
2010-09-30 10:25 ` potswa at mac dot com
2010-09-30 10:34 ` paolo.carlini at oracle dot com
2010-09-30 10:47 ` potswa at mac dot com
2010-09-30 11:00 ` paolo.carlini at oracle dot com
2010-09-30 11:10 ` potswa at mac dot com
2010-09-30 11:24 ` paolo.carlini at oracle dot com
2010-09-30 11:35 ` rguenth at gcc dot gnu.org
2010-09-30 14:48 ` hp at gcc dot gnu.org
2010-09-30 17:47 ` rguenth at gcc dot gnu.org
2010-10-01  3:15 ` hp at gcc dot gnu.org
2010-10-01 12:15 ` paolo.carlini at oracle dot com
2010-10-01 12:19 ` potswa at mac dot com
2010-10-01 16:31 ` paolo.carlini at oracle dot com
2010-10-04 23:52 ` [Bug testsuite/45841] " hp at gcc dot gnu.org
2010-10-04 23:59 ` hp at gcc dot gnu.org
2010-10-05  0:24 ` potswa at mac dot com
2010-10-05  1:58 ` hp at gcc dot gnu.org
2010-10-05  2:58 ` potswa at mac dot com
2010-10-05  4:02 ` hp at gcc dot gnu.org
2010-10-05  9:11 ` [Bug libstdc++/45841] " paolo.carlini at oracle dot com
2010-10-05 17:03 ` hp at gcc dot gnu.org
2010-10-05 17:06 ` paolo.carlini at oracle dot com
2010-10-05 17:24 ` potswa at mac dot com
2010-10-05 17:26 ` potswa at mac dot com
2010-10-05 18:56 ` hp at gcc dot gnu.org
2010-10-05 19:30 ` hp at gcc dot gnu.org
2010-10-05 20:10 ` potswa at mac dot com
2010-10-05 21:13 ` paolo.carlini at oracle dot com
2010-10-05 21:32 ` potswa at mac dot com
2010-10-05 21:51 ` hp at gcc dot gnu.org
2010-10-05 21:59 ` hp at gcc dot gnu.org
2010-10-05 22:29 ` paolo.carlini at oracle dot com
2010-10-05 22:47 ` potswa at mac dot com
2010-10-05 23:16 ` hp at gcc dot gnu.org
2010-10-05 23:29 ` hp at gcc dot gnu.org
2010-10-05 23:31 ` potswa at mac dot com [this message]
2010-10-05 23:34 ` paolo.carlini at oracle dot com
2010-10-05 23:38 ` potswa at mac dot com
2010-10-05 23:41 ` paolo.carlini at oracle dot com
2010-10-05 23:47 ` potswa at mac dot com
2010-10-05 23:49 ` paolo.carlini at oracle dot com
2010-10-05 23:52 ` hp at gcc dot gnu.org
2010-10-06  0:17 ` paolo at gcc dot gnu.org
2010-10-07 21:47 ` hp at gcc dot gnu.org
2010-10-07 22:15 ` hp at gcc dot gnu.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=20101005233100.r2uZ3wdGpu2RTEZzIIcdwi7_PM3U4sjls5de4zY12Vk@z \
    --to=gcc-bugzilla-noreply@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).