This is the mail archive of the gcc-patches@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: C++ PATCHes to run testsuite in C++14 mode

From: Jason Merrill <jason at redhat dot com>
To: Fabien Chêne <fabien dot chene at gmail dot com>
Cc: gcc-patches List <gcc-patches at gcc dot gnu dot org>
Date: Mon, 24 Mar 2014 23:44:32 -0400
Subject: Re: C++ PATCHes to run testsuite in C++14 mode
Authentication-results: sourceware.org; auth=none
References: <531A3D9B dot 1030203 at redhat dot com> <CAFH4-dheS1mybhq1pwCmZ4JSJxedoXfbx9kHHDmXrgFv_FFK7w at mail dot gmail dot com>

On 03/24/2014 05:06 PM, Fabien Chêne wrote:

2014-03-07 22:43 GMT+01:00 Jason Merrill <jason@redhat.com>:

The first patch changes the C++ testsuite to run in C++14 mode as well as
C++98 and C++11.


As a result, specifying { target c++11 } matches c++11 and c++1y mode.
{ target c++1y } matches c++1y only, and { target c++98 } matches c++98 only.
Is that correct ?

Everything is intended to mean "C++XX and up" now. But c++98 isn'tdefined, since it would be meaningless. And so it isn't used in testseither. So for c++98 only you can use c++98_only or { ! c++11 }.

The second patch splits up the running of dg.exp to avoid it running longer
than libstdc++ in parallel testing.


Incidentally, how does it affect testing time ?

On a highly parallel system, it doesn't affect testing time because oneof the chunks of libstdc++ tests still takes longer than any of thechunks of g++ tests.


Jason

References:
- C++ PATCHes to run testsuite in C++14 mode
  - From: Jason Merrill
- Re: C++ PATCHes to run testsuite in C++14 mode
  - From: Fabien Chêne

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