On Wed, Apr 04, 2018 at 03:47:18PM -0500, Bill Schmidt wrote:
> > If we (for GCC9?) want to create a spot for target C++ tests, we should
> > just add g++.target/<cpu>/ directories and add all the needed infrastructure
> > for those.
> >
> > Can you please revert the powerpc.exp change and move the test to
> > g++.dg/ext/ ? Thanks.
>
> Sure, I can -- I just want to point out that there is precedent here. I
> noticed
Thanks.
> that gcc.target/s390/s390.exp allows .C suffixes and there is one such
> (compile-only) test in that directory, so I assumed the framework was okay
> for this.
Yes, and apparently aarch64 and arm have a couple of *.C tests too.
Still it doesn't feel right, running C++ tests under make check-gcc rather
than check-g++ is just weird.
I think we should just introduce g++.target/ in GCC9 and move those tests
there, plus any g++.dg/ tests guarded for single targets only. g++.target
should do the -std=c++{98,11,14,17,2a} cycling etc.
Jakub
