public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bkoz at redhat dot com" <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 16:20:00 -0000 [thread overview] Message-ID: <20031222155701.7716.qmail@sources.redhat.com> (raw) In-Reply-To: <20030509131600.10703.ebotcazou@libertysurf.fr> ------- Additional Comments From bkoz at redhat dot com 2003-12-22 15:56 ------- Subject: Re: [3.3 regression] testsuite/27_io/istream_unformatted.cc fails I agree with Paolo's assessment. For the future, 3.4 is in good shape on Irix 6.5. (And the ancient versions of Solaris.) For the present, the failure is not a high-priority bug. The gcc-3_3-branch and mainline testsuite have diverged to the point that no mainline tests are getting back-ported to the 3_3-branch testsuite. It's entirely possible that the 3.3 branch code, which has had back-ports from 3.4, is not completely in sync with the 3.3.x testsuite code. Although a regrettable situation, I regard it as a temporary glitch due to the effort to fix up the libstdc++ test infrastructure happened after 3.2 and 3.3 branched. -benjamin -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10703
next prev parent reply other threads:[~2003-12-22 15:57 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 ` [Bug libstdc++/10703] [3.3/3.4 " mmitchel at gcc dot gnu dot org 2003-12-22 16:20 ` bkoz at redhat dot com [this message] 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=20031222155701.7716.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: 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).