Re: C++ testsuite PATCH to overhaul running of tests in C++11 mode

2012-01-21 Thread Jason Merrill
On 01/21/2012 06:02 AM, Richard Sandiford wrote: Does this mean that the { target c++98 } lines are acceptable in C++11, while the { xfail c++11 } lines are still errors in C++11, but aren't detected? Right. The reason for asking is that the line: g<(void (A::*)())&B::f>(); // { dg-erro

Re: C++ testsuite PATCH to overhaul running of tests in C++11 mode

2012-01-21 Thread Richard Sandiford
A mere two months after you posted the patch: Jason Merrill writes: > diff --git a/gcc/testsuite/g++.old-deja/g++.pt/ptrmem6.C > b/gcc/testsuite/g++.old-deja/g++.pt/ptrmem6.C > index 8802e98..19f1591 100644 > --- a/gcc/testsuite/g++.old-deja/g++.pt/ptrmem6.C > +++ b/gcc/testsuite/g++.old-deja/g+

Re: C++ testsuite PATCH to overhaul running of tests in C++11 mode

2011-11-09 Thread Jason Merrill
On 11/09/2011 04:01 PM, Fabien ChĂȘne wrote: Nice, but ... is there a way to launch the testsuite with only one mode at a time ? Not currently. Jason

Re: C++ testsuite PATCH to overhaul running of tests in C++11 mode

2011-11-09 Thread Fabien ChĂȘne
Hi, 2011/11/9 Jason Merrill : > On 11/09/2011 01:02 PM, Joseph S. Myers wrote: >> >> To confirm: what do the PASS or FAIL lines look like? > > For tests run in both modes, they look like > > PASS: g++.dg/whatever -std=c++98 > PASS: g++.dg/whatever -std=c++11 Nice, but ... is there a way to launch

Re: C++ testsuite PATCH to overhaul running of tests in C++11 mode

2011-11-09 Thread Jason Merrill
On 11/09/2011 01:02 PM, Joseph S. Myers wrote: To confirm: what do the PASS or FAIL lines look like? For tests run in both modes, they look like PASS: g++.dg/whatever -std=c++98 PASS: g++.dg/whatever -std=c++11 Jason

Re: C++ testsuite PATCH to overhaul running of tests in C++11 mode

2011-11-09 Thread Joseph S. Myers
On Wed, 9 Nov 2011, Jason Merrill wrote: > While working on an earlier PR I noticed that make check-c++0x wasn't actually > running a lot of tests in C++11 mode because the -std=c++11 that it added came > before the default arguments, so any test without a { dg-options } line would > still be run