public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: "B. Kosnik" <bkoz@nabi.net>
Cc: Joe Buck <Joe.Buck@synopsys.com>, mark@codesourcery.com, gcc@gcc.gnu.org
Subject: Re: GCC 3.2 Prerelease
Date: Wed, 07 Aug 2002 07:43:00 -0000	[thread overview]
Message-ID: <20020807104039.A20654@disaster.basement.lan> (raw)
In-Reply-To: <20020806131024.A10378@disaster.basement.lan>

On Tue, Aug 06, 2002 at 01:10:24PM -0400, Phil Edwards wrote:
> On Mon, Aug 05, 2002 at 06:07:25PM -0700, B. Kosnik wrote:
> > There are 155 g++ fails, and 15 libstdc++ fails, when the 3.3
> > libstdc++.so is used with the 3.2 toolchain.
> 
> I'm finally far enough recovered from a fatal hard drive crash that I can
> try and do this test today.

Took longer than I thought.

For me, when the 3.2 libstdc++.so is used with the 3.3 compiler, I see

    fenric 27% diff results-3.2 results-3.3
    29d28
    < FAIL: backward/strstream_members.cc execution test
    33,34c32,33
    < # of expected passes          414
    < # of unexpected failures      3
    ---
    > # of expected passes          415
    > # of unexpected failures      2
    fenric 28%

the expected failure.

When the 3.3 libstdc++.so is used with the 3.2 compiler, I see no differences
at all.  Huh.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams

  reply	other threads:[~2002-08-07  7:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 11:46 B. Kosnik
2002-08-05 15:45 ` Joe Buck
2002-08-05 18:07   ` B. Kosnik
2002-08-05 19:02     ` H. J. Lu
2002-08-06  5:54     ` Daniel Jacobowitz
2002-08-06  8:07       ` Daniel Jacobowitz
2002-08-06 10:07         ` B. Kosnik
2002-08-06  8:47       ` Mark Mitchell
2002-08-06 10:04         ` B. Kosnik
2002-08-06 10:10     ` Phil Edwards
2002-08-07  7:43       ` Phil Edwards [this message]
2002-08-06 11:05     ` H. J. Lu
2002-08-06 11:21       ` Mark Mitchell
2002-08-06 11:30         ` H. J. Lu
2002-08-06 11:53           ` Neil Booth
2002-08-06 11:42         ` Joe Buck
2002-08-06 11:56           ` H. J. Lu
2002-08-06 11:46         ` Graham Stott
2002-08-06 11:37       ` Joe Buck
2002-08-06 11:59         ` H. J. Lu
2002-08-06 12:15           ` H. J. Lu
2002-08-06 12:17             ` H. J. Lu
2002-08-06 12:25               ` David Edelsohn
2002-08-06 14:14                 ` Joe Buck
2002-08-06 20:29                   ` Mark Mitchell
2002-08-06 22:17                     ` B. Kosnik
2002-08-06 12:24         ` H. J. Lu
2002-08-06 12:37           ` H. J. Lu
  -- strict thread matches above, loose matches on Subject: below --
2002-08-09 11:48 Mark Mitchell
2002-08-04 20:10 Mark Mitchell

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=20020807104039.A20654@disaster.basement.lan \
    --to=phil@jaj.com \
    --cc=Joe.Buck@synopsys.com \
    --cc=bkoz@nabi.net \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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).