* Re: g++ failures
@ 1999-03-16 13:36 Mike Stump
1999-03-31 23:46 ` Mike Stump
0 siblings, 1 reply; 6+ messages in thread
From: Mike Stump @ 1999-03-16 13:36 UTC (permalink / raw)
To: hjl; +Cc: egcs, jason
> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: g++ failures
1999-03-16 13:36 g++ failures Mike Stump
@ 1999-03-31 23:46 ` Mike Stump
0 siblings, 0 replies; 6+ messages in thread
From: Mike Stump @ 1999-03-31 23:46 UTC (permalink / raw)
To: hjl; +Cc: egcs, jason
> 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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: g++ failures
1999-03-16 6:54 ` H.J. Lu
@ 1999-03-31 23:46 ` H.J. Lu
0 siblings, 0 replies; 6+ messages in thread
From: H.J. Lu @ 1999-03-31 23:46 UTC (permalink / raw)
To: mrs; +Cc: jason, egcs
>
> 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)
^ permalink raw reply [flat|nested] 6+ messages in thread
* g++ failures
1999-03-16 5:35 mrs
[not found] ` < 199903161335.FAA02915@wrs.com >
@ 1999-03-31 23:46 ` mrs
1 sibling, 0 replies; 6+ messages in thread
From: mrs @ 1999-03-31 23:46 UTC (permalink / raw)
To: jason; +Cc: egcs
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: g++ failures
[not found] ` < 199903161335.FAA02915@wrs.com >
@ 1999-03-16 6:54 ` H.J. Lu
1999-03-31 23:46 ` H.J. Lu
0 siblings, 1 reply; 6+ messages in thread
From: H.J. Lu @ 1999-03-16 6:54 UTC (permalink / raw)
To: mrs; +Cc: jason, egcs
>
> 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)
^ permalink raw reply [flat|nested] 6+ messages in thread
* g++ failures
@ 1999-03-16 5:35 mrs
[not found] ` < 199903161335.FAA02915@wrs.com >
1999-03-31 23:46 ` mrs
0 siblings, 2 replies; 6+ messages in thread
From: mrs @ 1999-03-16 5:35 UTC (permalink / raw)
To: jason; +Cc: egcs
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~1999-03-31 23:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1999-03-16 13:36 g++ failures Mike Stump
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
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).