From: Kewen Lin <linkw@linux.ibm.com>
Date: Tue, 21 May 2024 02:01:08 +0000 (-0500)
Subject: testsuite, rs6000: Make powerpc_altivec consider current_compiler_flags [PR114842]
X-Git-Tag: basepoints/gcc-16~8837
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3bb8cdbd60cdb4dab45b97235dc045d65555b0a1;p=thirdparty%2Fgcc.git

testsuite, rs6000: Make powerpc_altivec consider current_compiler_flags [PR114842]

As noted in PR114842, most of the test cases which require
effective target check powerpc_altivec_ok actually care
about if ALTIVEC feature is enabled, and they should adopt
effective target powerpc_altivec instead.  By considering
we already have a number of test cases having explicit
-maltivec in dg-options etc., to keep them still be tested
as before even without altivec enabled by default, this
patch makes powerpc_altivec consider current_compiler_flags
like what we do for powerpc_vsx.

	PR testsuite/114842

gcc/testsuite/ChangeLog:

	* lib/target-supports.exp (check_effective_target_powerpc_altivec):
	Take current_compiler_flags into account.
---

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index 8689c11214d..3f0f8532dc3 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -7323,7 +7323,7 @@ proc check_effective_target_sparc_vis { } {
 	    #else
 	    int dummy;
 	    #endif
-	}]
+	} [current_compiler_flags]]
     } else {
 	return 0
     }