[PATCH] vect-pragma-target-1.C: Compile with -march=x86-64

"H.J. Lu" <[email protected]>
Newsgroups gmane.comp.gcc.patches
Message-ID <CAMe9rOr=bhA50qVUoMWuknP_Rv8H7akaky--ytusn66cfdtjYw@mail.gmail.com>
ompile vect-pragma-target-1.C with -march=x86-64 so that AVX512 isn't
enabled on AVX512 machines when GCC is configured with

--with-arch=native --with-cpu=native

PR testsuite/126923
* g++.target/i386/vect-pragma-target-1.C (dg-options): Add
-march=x86-64.

-- 
H.J.
0001-vect-pragma-target-1.C-Compile-with-march-x86-64.patch (text/x-patch, 1.4 KB)
From d51f54135220758413c293342bb618f5dc2e06a1 Mon Sep 17 00:00:00 2001
From: "H.J. Lu" <[email protected]>
Date: Tue, 18 Aug 2026 09:06:32 +0800
Subject: [PATCH] vect-pragma-target-1.C: Compile with -march=x86-64

Compile vect-pragma-target-1.C with -march=x86-64 so that AVX512 isn't
enabled on AVX512 machines when GCC is configured with

--with-arch=native --with-cpu=native

	PR testsuite/126923
	* g++.target/i386/vect-pragma-target-1.C (dg-options): Add
	-march=x86-64.

Signed-off-by: H.J. Lu <[email protected]>
---
 gcc/testsuite/g++.target/i386/vect-pragma-target-1.C | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/g++.target/i386/vect-pragma-target-1.C b/gcc/testsuite/g++.target/i386/vect-pragma-target-1.C
index 2f360cf50e1..1833c0806ee 100644
--- a/gcc/testsuite/g++.target/i386/vect-pragma-target-1.C
+++ b/gcc/testsuite/g++.target/i386/vect-pragma-target-1.C
@@ -1,5 +1,5 @@
 /* { dg-do compile { target { i?86-*-* x86_64-*-* } } }                 */
-/* { dg-options "-O0" }                                                 */
+/* { dg-options "-O0 -march=x86-64" }                                   */
 /* { dg-final { scan-assembler-times "paddd.+xmm\[0-9]+"        1 } }   */
 /* { dg-final { scan-assembler-times "vfmadd132ps.+ymm\[0-9]+"  1 } }   */
 /* { dg-final { scan-assembler-times "vpaddw.+zmm\[0-9]+"       1 } }   */
-- 
2.55.0
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.