Re: [PATCH] Make check_effective_target_c++ work for libstdc++

2016-12-07 Thread Ville Voutilainen
On 7 December 2016 at 13:24, Jonathan Wakely wrote: > I'd like to backport this (r238916) to the gcc-6-branch too. > > It's been very useful on trunk. The only problems are when we backport > new tests from trunk to the branch and forget that the effective > target doesn't

Re: [PATCH] Make check_effective_target_c++ work for libstdc++

2016-12-07 Thread Jonathan Wakely
On 29/07/16 20:43 +0100, Jonathan Wakely wrote: I've been working on some changes to let the libstdc++ testsuite use the same approach as G++ to specify a minimum language dialect for tests. That means instead of hardcoding { dg-options "-std=gnu++11" } we can use { dg-do run { target c++11 } }

Re: [PATCH] Make check_effective_target_c++ work for libstdc++

2016-07-29 Thread Mike Stump
On Jul 29, 2016, at 12:43 PM, Jonathan Wakely wrote: > > I've been working on some changes to let the libstdc++ testsuite use > the same approach as G++ to specify a minimum language dialect for > tests. That means instead of hardcoding { dg-options "-std=gnu++11" } > we can

[PATCH] Make check_effective_target_c++ work for libstdc++

2016-07-29 Thread Jonathan Wakely
I've been working on some changes to let the libstdc++ testsuite use the same approach as G++ to specify a minimum language dialect for tests. That means instead of hardcoding { dg-options "-std=gnu++11" } we can use { dg-do run { target c++11 } } and the test will be run for any implicit or