This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Does anyone check libstdc++-v3 failures in gcc 3.0?

To: Gabriel Dos Reis <Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr>
Subject: Re: Does anyone check libstdc++-v3 failures in gcc 3.0?
From: Phil Edwards <pedwards at disaster dot jaj dot com>
Date: Mon, 16 Apr 2001 03:34:54 -0400
Cc: "H . J . Lu" <hjl at lucon dot org>, gcc at gcc dot gnu dot org
References: <20010415204949.A6524@lucon.org> <20010416001449.A29011@disaster.jaj.com> <fln19h2u03.fsf@sel.cmla.ens-cachan.fr>

On Mon, Apr 16, 2001 at 09:17:48AM +0200, Gabriel Dos Reis wrote:
> Phil Edwards <pedwards@disaster.jaj.com> writes:
> | 
> | XFAILs.  The mkcheck script doesn't know about XFAIL yet.
> 
> But the new testing framework does know.

Yes.  One more reason in favor of merging trunk to branch for the library.


Phil

-- 
pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools.  Fools are protected by more capable fools.

References:
- Does anyone check libstdc++-v3 failures in gcc 3.0?
  - From: H . J . Lu
- Re: Does anyone check libstdc++-v3 failures in gcc 3.0?
  - From: Phil Edwards
- Re: Does anyone check libstdc++-v3 failures in gcc 3.0?
  - From: Gabriel Dos Reis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]