From mboxrd@z Thu Jan  1 00:00:00 1970
From: mrs@wrs.com
To: jason@cygnus.com
Cc: egcs@cygnus.com
Subject: g++ failures
Date: Tue, 16 Mar 1999 05:35:00 -0000
Message-id: <199903161335.FAA02915@wrs.com>
X-SW-Source: 1999-03/msg00542.html

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.

From mboxrd@z Thu Jan  1 00:00:00 1970
From: mrs@wrs.com
To: jason@cygnus.com
Cc: egcs@cygnus.com
Subject: g++ failures
Date: Wed, 31 Mar 1999 23:46:00 -0000
Message-ID: <199903161335.FAA02915@wrs.com>
X-SW-Source: 1999-03n/msg00547.html
Message-ID: <19990331234600.i_T5pFpsXD7lNjoJ1M9z-TPpwGHxqeLp4baaY_jRypo@z>

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.