This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: 27_io/istream_extractor_arith.cc fixup
- From: Andreas Schwab <schwab at suse dot de>
- To: Paolo Carlini <pcarlini at unitus dot it>
- Cc: libstdc++ at gcc dot gnu dot org
- Date: Thu, 31 Jan 2002 11:55:48 +0100
- Subject: Re: 27_io/istream_extractor_arith.cc fixup
- References: <200201291947.g0TJlR302024@fillmore.constant.com><3C5733E5.5A2A6BCD@unitus.it> <jeit9ki3p3.fsf@sykes.suse.de><3C57BF3C.7070907@unitus.it>
Paolo Carlini <pcarlini@unitus.it> writes:
|> Andreas Schwab wrote:
|>
|> >Paolo Carlini <pcarlini@unitus.it> writes:
|> >
|> >|> What *really* puzzles me is this:
|> > |> |> http://gcc.gnu.org/ml/gcc-testresults/2002-01/msg00582.html
|> > |> |> How possibly, ostream_inserter_arith.cc can fail now on ia64? It
|> > did'nt fail
|> >|> before enabling test03, then Andreas tested positively the patch above, and then
|> >|> it fails now?!?
|> >
|> >There were some conflicts with the change I used locally, due to some
|> >stupid mailer that has mangled whitespace.
|> >
|> I see.
|> Therefore, if you can confirm that indeed the testcase is failing now with
|> a freshly updated source from CVS, could you please post some details? It
|> would be important to see the relevant section of libstdc++-v3.log in
|> order to debug it.
As you may have seen already, the test is working again after removing
the conflict markers.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."