From: hjl@lucon.org (H.J. Lu)
To: mrs@wrs.com
Cc: jason@cygnus.com, egcs@cygnus.com
Subject: Re: g++ failures
Date: Wed, 31 Mar 1999 23:46:00 -0000 [thread overview]
Message-ID: <m10MvEs-000ErMC@ocean.lucon.org> (raw)
Message-ID: <19990331234600.j3oqoYxgVQPbzwybC4Ksb4KfFkciTuriD2spNAy_PB0@z> (raw)
In-Reply-To: <199903161335.FAA02915@wrs.com>
>
> I see you checked in:
>
> 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
>
> but they aren't marked as expected to fail. These are the only
> unexpected failures (for me) for g++ currently, and it would be nice
> to get these cleaned up.
>
> I see this on i586-pc-linux-gnulibc1.
>
Get the gas snapshot. It is needed for those.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1999-03-31 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 5:35 mrs
[not found] ` < 199903161335.FAA02915@wrs.com >
1999-03-16 6:54 ` H.J. Lu [this message]
1999-03-31 23:46 ` H.J. Lu
1999-03-31 23:46 ` mrs
1999-03-16 13:36 Mike Stump
1999-03-31 23:46 ` Mike Stump
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=m10MvEs-000ErMC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=egcs@cygnus.com \
--cc=jason@cygnus.com \
--cc=mrs@wrs.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).