RE: [PATCH] vect-pragma-target-2.C: Compile with -march=x86-64
"Liu, Hongtao" <[email protected]>
| Newsgroups | gmane.comp.gcc.patches |
|---|---|
| Message-ID | <DS4PPF240F42FB736D66929980EC46973E5E5A62@DS4PPF240F42FB7.namprd11.prod.outlook.com> |
> -----Original Message----- > From: Liu, Hongtao > Sent: Tuesday, August 18, 2026 9:43 AM > To: H.J. Lu <[email protected]>; GCC Patches <[email protected]>; > Uros Bizjak <[email protected]> > Subject: RE: [PATCH] vect-pragma-target-2.C: Compile with -march=x86-64 > > > -----Original Message----- > > From: H.J. Lu <[email protected]> > > Sent: Tuesday, August 18, 2026 9:12 AM > > To: GCC Patches <[email protected]>; Uros Bizjak > > <[email protected]>; Liu, Hongtao <[email protected]> > > Subject: [PATCH] vect-pragma-target-2.C: Compile with -march=x86-64 > > > > Compile vect-pragma-target-2.C with -march=x86-64 so that x86-64-v2 > > and above features aren't enabled on x86-64-v4 machines when GCC is > > configured with > > > > --with-arch=native --with-cpu=native > > There are quite a few test cases that fail under --with-arch=native. As I > understand it, the primary intent of using --with-arch=native is to serve as an > indicator for detecting genuine regressions, rather than to actively investigate > and fix those individual failures. Just to clarify, I am not opposed to the patch itself, but rather discussing the strategy around regression testing with --with-arch=native. > > > > > PR testsuite/126923 > > * g++.target/i386/vect-pragma-target-2.C (dg-options): Add -march=x86- > 64. > > > > -- > > H.J.