[RS6000] Don't be too clever with dg-do run and dg-do compile

[Segher Boessenkool]

On Wed, Oct 28, 2020 at 09:20:56PM +1030, Alan Modra wrote:
> Otherwise some versions of dejagnu go ahead and run the vsx tests
> below when they should not.  To best cope with older dejagnu, put
> "run" before "compile", the idea being that if the second dg-do always
> wins then that won't cause fails.

If they are mutually exclusive, does the order still matter?  (Just FMI.)

> The altivec tests also need -save-temps for the scan-assembler test to
> occur when vms_hw.

> Regression tested powerpc64le-linux and powerpc64-linux.  OK?
> 
> 	* gcc.target/powerpc/vsx-load-element-extend-char.c: Put "dg-do run"
> 	before "dg-do compile", and make them mutually exclusive.
> 	* gcc.target/powerpc/vsx-load-element-extend-int.c: Likewise.
> 	* gcc.target/powerpc/vsx-load-element-extend-longlong.c: Likewise.
> 	* gcc.target/powerpc/vsx-load-element-extend-short.c: Likewise.
> 	* gcc.target/powerpc/vsx-store-element-truncate-char.c: Likewise.
> 	* gcc.target/powerpc/vsx-store-element-truncate-int.c: Likewise.
> 	* gcc.target/powerpc/vsx-store-element-truncate-longlong.c: Likewise.
> 	* gcc.target/powerpc/vsx-store-element-truncate-short.c: Likewise.
> 	* gcc.target/powerpc/altivec-consts.c: Likewise, add -save-temps.
> 	* gcc.target/powerpc/le-altivec-consts.c: Likewise.

Okay for trunk.  Thanks!


Segher