From: Robert Lipe <robertl@dgii.com>
To: Mumit Khan <khan@xraylith.wisc.edu>
Cc: Theodore Papadopoulo <Theodore.Papadopoulo@sophia.inria.fr>,
egcs@cygnus.com, Max Lawson <mlawson@drfmc.ceng.cea.fr>
Subject: Re: Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1]
Date: Mon, 01 Dec 1997 11:33:00 -0000 [thread overview]
Message-ID: <19971201133143.48258@dgii.com> (raw)
In-Reply-To: <Pine.HPP.3.96.971201125146.15682A-100000@hp2.xraylith.wisc.edu>
> > From the other reports I see, you seem more to be the exception than
> > the average case or maybe your are the only one with RH4.1 which seems
>
> for the results from Peter Schmid, posted on Nov. 29. He also does not see
> the failure for typename5.C that you see. Max Lawson's message that shows
Perhaps there's some sort of slippery x86 thing going on here, becuase
typename5.C fails on i586-pc-sco3.2v5.0.4, too. See:
http://www.cygnus.com/ml/egcs/1997-Nov/0950.html
Interestingly, it seems to be a recent failure.
$ grep typename5.C */*.sum
coff-971123/g++.sum:PASS: g++.pt/typename5.C (test for excess errors)
coff-971129/g++.sum:FAIL: g++.pt/typename5.C (test for excess errors)
elf-971123/g++.sum:PASS: g++.pt/typename5.C (test for excess errors)
elf-971129/g++.sum:FAIL: g++.pt/typename5.C (test for excess errors)
next prev parent reply other threads:[~1997-12-01 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-01 2:36 egcs-971127: testsuite results on i586-pc-linux-gnulibc1 Max Lawson
1997-12-01 7:38 ` Theodore Papadopoulo
1997-12-01 11:03 ` Typename5.C failure i386-linux-gnulibc1 [Re: egcs-971127: testsuiteresults on i586-pc-linux-gnulibc1] Mumit Khan
1997-12-01 11:33 ` Robert Lipe [this message]
1997-12-01 19:30 ` Mumit Khan
1997-12-01 17:20 Max Lawson
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=19971201133143.48258@dgii.com \
--to=robertl@dgii.com \
--cc=Theodore.Papadopoulo@sophia.inria.fr \
--cc=egcs@cygnus.com \
--cc=khan@xraylith.wisc.edu \
--cc=mlawson@drfmc.ceng.cea.fr \
/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).