From: mrs@wrs.com (Mike Stump)
To: hjl@lucon.org
Cc: egcs@cygnus.com, jason@cygnus.com
Subject: Re: g++ failures
Date: Tue, 16 Mar 1999 13:36:00 -0000 [thread overview]
Message-ID: <199903162135.NAA09524@kankakee.wrs.com> (raw)
> From: hjl@lucon.org (H.J. Lu)
> To: mrs@wrs.com
> Date: Tue, 16 Mar 1999 06:54:38 -0800 (PST)
> Cc: jason@cygnus.com, egcs@cygnus.com
> > FAIL: g++.dg/special/conpr-1.C execution test
> > FAIL: g++.dg/special/conpr-2.C execution test
> > FAIL: g++.dg/special/conpr-3.C execution test
> Get the gas snapshot. It is needed for those.
Ok. I think this is a non-issue then. We can require people grab a
newer gas/binutils to get `perfect' results. Sorry for the false
alarm.
WARNING: multiple messages have this Message-ID
From: mrs@wrs.com (Mike Stump)
To: hjl@lucon.org
Cc: egcs@cygnus.com, jason@cygnus.com
Subject: Re: g++ failures
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <199903162135.NAA09524@kankakee.wrs.com> (raw)
Message-ID: <19990331234600.bgYL15H_fDdOHEkc8qMsWvRumzvBuFH15XfzVyMrl8c@z> (raw)
> From: hjl@lucon.org (H.J. Lu)
> To: mrs@wrs.com
> Date: Tue, 16 Mar 1999 06:54:38 -0800 (PST)
> Cc: jason@cygnus.com, egcs@cygnus.com
> > FAIL: g++.dg/special/conpr-1.C execution test
> > FAIL: g++.dg/special/conpr-2.C execution test
> > FAIL: g++.dg/special/conpr-3.C execution test
> Get the gas snapshot. It is needed for those.
Ok. I think this is a non-issue then. We can require people grab a
newer gas/binutils to get `perfect' results. Sorry for the false
alarm.
next reply other threads:[~1999-03-16 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 13:36 Mike Stump [this message]
1999-03-31 23:46 ` Mike Stump
-- strict thread matches above, loose matches on Subject: below --
1999-03-16 5:35 mrs
[not found] ` < 199903161335.FAA02915@wrs.com >
1999-03-16 6:54 ` H.J. Lu
1999-03-31 23:46 ` H.J. Lu
1999-03-31 23:46 ` mrs
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=199903162135.NAA09524@kankakee.wrs.com \
--to=mrs@wrs.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=jason@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).