On Wed, Aug 24, 2022 at 01:11:39PM +0800, HAO CHEN GUI wrote: > On 23/8/2022 下午 10:26, Segher Boessenkool wrote: > > On Fri, Aug 19, 2022 at 10:35:54AM +0800, HAO CHEN GUI wrote: > >> --- a/gcc/testsuite/gcc.target/powerpc/bfp/scalar-extract-exp-0.c > >> +++ b/gcc/testsuite/gcc.target/powerpc/bfp/scalar-extract-exp-0.c > >> @@ -1,7 +1,8 @@ > >> /* { dg-do compile { target { powerpc*-*-* } } } */ > >> -/* { dg-require-effective-target lp64 } */ > >> -/* { dg-require-effective-target powerpc_p9vector_ok } */ > >> /* { dg-options "-mdejagnu-cpu=power9" } */ > >> +/* { dg-additional-options "-mpowerpc64" { target { powerpc*-*-linux* && > >> ilp32 } } } */ > > > > You can add this always. It is default on 64-bit systems, but it is > > simpler to just always add it: > > /* { dg-additional-options "-mpowerpc64" } */ > > > > Or are there subtargets that will error on this? > Yes, AIX fails if TARGET_POWERPC64 is set and TARGET_64BIT is not set. > So I add "-mpowerpc64" for Linux 32-bit environment.
Aha. But you can add it for all linux: /* { dg-additional-options "-mpowerpc64" { target powerpc*-*-linux* } } */ (or *-*-linux* even, everything in gcc.target/powerpc is known to be powerpc*-*-* already). Not that it matters at all here, as the other thread shows :-), but for the future: run testcases wherever possible (and reasonable), and in the same vein, try not to specialise option when you do not have to. Doing this makes testing much less work, makes it easier to have reasonable coverage. Segher