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]
Other format:	[Raw text]

Re: Using DejaGNU on GCC's Testsuite

From: Andreas Schwab <schwab at linux-m68k dot org>
To: PARAT Didier <didier dot parat at fr dot thalesgroup dot com>
Cc: "gcc\ at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Tue, 21 Aug 2012 13:52:18 +0200
Subject: Re: Using DejaGNU on GCC's Testsuite
References: <19588_1345474116_50324E44_19588_3626_1_49CF97100DDD4B4A9C4DC89905CA59A3101B400A46@THSONEA01CMS07P.one.grp> <m28vd8ehd0.fsf@igel.home> <28210_1345549022_503372DE_28210_4651_1_49CF97100DDD4B4A9C4DC89905CA59A3101B401367@THSONEA01CMS07P.one.grp>

PARAT Didier <didier.parat@fr.thalesgroup.com> writes:

> If no options are passed to DejaGNU for the GCC testsuite,
> it will take default ones in testsuite/lib/gcc-dg.exp and 
> testsuite/lib/c-torture.exp. So 'dg' tests, as well as c-torture,
> use basic options.

gcc.dg/dg.exp doesn't use gcc-dg-runtest (and never did).

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- Using DejaGNU on GCC's Testsuite
  - From: PARAT Didier
- Re: Using DejaGNU on GCC's Testsuite
  - From: Andreas Schwab
- RE: Using DejaGNU on GCC's Testsuite
  - From: PARAT Didier

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