From: Joe Buck <jbuck@synopsys.com>
To: egcs@cygnus.com
Subject: Re: Results for haifa-disabled egcs-970828 g++ testsuite on sparc-sun-solaris2.5
Date: Sat, 30 Aug 1997 05:43:52 -0000 [thread overview]
Message-ID: <199708300543.WAA18204@atrus.synopsys.com> (raw)
In-Reply-To: orn2m0fe0d.fsf@sunsite.dcc.unicamp.br
Alexandre:
> >> The tests that have failed are compile-time ones, and I can assure
> >> that my configuration does run tests.
Me:
> > Please try explicitly hand-running one of the tests I report as failing and
> > your report as passing.
Alexandre again:
> I looked at the test files, and found out they all #include header
> files that are only installed with libg++, which I had installed with
> egcs-970822.
I suggest that any tests that use libg++ headers that are not in libstdc++
either be re-written to use only standard headers, or else they can be
moved to the libg++ test suite. If anyone is worried about losing a
test, we can do both: move the exact test to libg++/testsuite and leave
the rewritten test in the g++ test suite.
> Is there anyway to tell runtest that `it is ok if this error occurs,
> but it is not an expected one'. It should be counted as an
> unsupported test, IMO.
I don't think that is a good idea. Either the tests should be rewritten
or they should be moved to the libg++ test suite; for most of them
a rewrite is easy.
next reply other threads:[~1997-08-30 5:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-30 5:43 Joe Buck [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-08-30 5:06 libI77 fmt uncleanliness Richard Henderson
1997-08-30 5:14 ` Results for haifa-disabled egcs-970828 g++ testsuite on sparc-sun-solaris2.5 Alexandre Oliva
1997-08-30 2:06 Joern Rennecke
1997-08-30 2:06 New GCC ports? Michael P. Hayes
1997-08-30 2:20 ` Results for haifa-disabled egcs-970828 g++ testsuite on sparc-sun-solaris2.5 Alexandre Oliva
1997-08-30 0:51 Joe Buck
1997-08-29 23:32 Alexandre Oliva
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=199708300543.WAA18204@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.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).