This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Spurious libstdc++ testsuite failures because of truncated buffered output

From: Andreas Schwab <schwab at linux-m68k dot org>
To: Diego Novillo <dnovillo at google dot com>
Cc: gcc at gnu dot org, libstdc++ at gcc dot gnu dot org
Date: Fri, 18 Mar 2011 19:05:39 +0100
Subject: Re: Spurious libstdc++ testsuite failures because of truncated buffered output
References: <AANLkTim+0aYi-eYTa6S0HSmyd6HeK_MJ65ALiKsdQtkx@mail.gmail.com> <m37hbws9ry.fsf@redhat.com> <AANLkTin+NSN3xNzKuwk7gne-uvNiG2vPcSWwUq2uMHq3@mail.gmail.com>

Diego Novillo <dnovillo@google.com> writes:

> Thanks, but I don't think match_max affects this.  It's the output
> from the compiler that is being truncated.

I don't see that problem on powerpc-linux (and I couldn't find any such
failure on gcc-testresults).

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- Re: Spurious libstdc++ testsuite failures because of truncated buffered output
  - From: Diego Novillo

References:
- Spurious libstdc++ testsuite failures because of truncated buffered output
  - From: Diego Novillo
- Re: Spurious libstdc++ testsuite failures because of truncated buffered output
  - From: Andreas Schwab
- Re: Spurious libstdc++ testsuite failures because of truncated buffered output
  - From: Diego Novillo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]