public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/10703] [3.3/3.4 regression] testsuite/27_io/istream_unformatted.cc fails
Date: Mon, 22 Dec 2003 05:54:00 -0000	[thread overview]
Message-ID: <20031222053314.20120.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030509131600.10703.ebotcazou@libertysurf.fr>


------- Additional Comments From mmitchel at gcc dot gnu dot org  2003-12-22 05:33 -------
I'm not eager to reopen this PR.

I suppose that technically, we should reopen it on the basis of the IRIX 6.5
failure.  However, I suspect that the fix may be to determine that IRIX 6.5
should no longer be a primary evaluation platform; it's not a very popular
platform any more.  In practice, this PR will not be fixed until someone with an
IRIX 6.5 system figures out what is going wrong.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
  GCC build triplet|sparc-sun-solaris2.6        |
 GCC target triplet|sparc-sun-solaris2.6        |sparc-sun-solaris2.6 mips-
                   |                            |sgi-irix6.5
         Resolution|WONTFIX                     |
            Summary|[3.3 regression]            |[3.3/3.4 regression]
                   |testsuite/27_io/istream_unfo|testsuite/27_io/istream_unfo
                   |rmatted.cc fails            |rmatted.cc fails
   Target Milestone|3.3.3                       |3.4.0


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


  parent reply	other threads:[~2003-12-22  5:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030509131600.10703.ebotcazou@libertysurf.fr>
2003-06-08  7:55 ` [Bug libstdc++/10703] [3.3 regression] [Solaris] 27_io/istream_unformatted.cc fails on Sparc/Solaris 2.5.1 and 2.6 dhazeghi@yahoo.com
2003-06-08 19:03 ` pinskia@physics.uc.edu
2003-06-17 21:15 ` bangerth@dealii.org
2003-06-24 22:47 ` bangerth at dealii dot org
2003-07-14 23:06 ` mmitchel at gcc dot gnu dot org
2003-10-16  9:46 ` [Bug libstdc++/10703] [3.3 regression] testsuite/27_io/istream_unformatted.cc fails mmitchel at gcc dot gnu dot org
2003-12-21 18:58 ` gdr at gcc dot gnu dot org
2003-12-21 21:40 ` paolo at gcc dot gnu dot org
2003-12-21 21:53 ` gdr at gcc dot gnu dot org
2003-12-21 21:56 ` gdr at integrable-solutions dot net
2003-12-21 22:08 ` ebotcazou at gcc dot gnu dot org
2003-12-22  5:32 ` ghazi at caip dot rutgers dot edu
2003-12-22  5:54 ` mmitchel at gcc dot gnu dot org [this message]
2003-12-22 16:20 ` [Bug libstdc++/10703] [3.3/3.4 " bkoz at redhat dot com
2004-01-01  6:01 ` pinskia at gcc dot gnu dot org
2004-01-21 14:07 ` [Bug libstdc++/10703] [3.3/3.4/3.5 " ebotcazou at gcc dot gnu dot org
2004-02-05  6:30 ` [Bug libstdc++/10703] [3.3 " rsandifo at gcc dot gnu dot org
2004-02-05 16:49 ` pinskia 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=20031222053314.20120.qmail@sources.redhat.com \
    --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).