From: mrs@wrs.com (Mike Stump)
To: egcs@cygnus.com
Subject: Re: egcs-971201: testsuite results for i586-pc-linux-gnulibc1
Date: Tue, 02 Dec 1997 18:18:00 -0000 [thread overview]
Message-ID: <199712030125.RAA06256@kankakee.wrs.com> (raw)
> Date: Tue, 2 Dec 1997 16:34:57 +0100
> From: Max Lawson <mlawson@drfmc.ceng.cea.fr>
> To: egcs@cygnus.com
> Here are the results for the last snapshot.
> XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
> XPASS: g++.mike/dyncast1.C Execution test
> XPASS: g++.mike/dyncast2.C Execution test
Ok, I already mentioned the fix for the g++.jason/destruct3.C problem,
it is really safe, I think it should be included in the release.
Likewise, the fix for the only other two is in:
http://www.cygnus.com/ml/egcs/1997-Nov/0197.html
and it is so safe! It involves 0 changes to any compiler code, just
the testsuite, so it in theory cannot hurt the release in any
substantial way. I think it should be included just for the `feeling
of well being'. I mean, we want the air of quality, right?
next reply other threads:[~1997-12-02 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-02 18:18 Mike Stump [this message]
[not found] <199712030125.RAA06256.cygnus.egcs@kankakee.wrs.com>
1997-12-02 21:12 ` Jason Merrill
-- strict thread matches above, loose matches on Subject: below --
1997-12-02 9:56 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=199712030125.RAA06256@kankakee.wrs.com \
--to=mrs@wrs.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).