public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH (pushed)] x86: fix VENDOR_MAX enum value
@ 2022-10-24 18:24 Martin Liška
  0 siblings, 0 replies; only message in thread
From: Martin Liška @ 2022-10-24 18:24 UTC (permalink / raw)
  To: gcc-patches

Hi.

The following patch fixes detection of VENDOR_CENTAUR CPU vendors when -march=native is used.
Problem what that BUILTIN_VENDOR_MAX dropped the current enum value to VENDOR_OTHER (4)
and thus VENDOR_MAX was 5 and not 7.

Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
I'm going to push it as obvious.

            PR target/107364
    
    gcc/ChangeLog:
    
            * common/config/i386/i386-cpuinfo.h (enum processor_vendor):
              Reorder enum values as BUILTIN_VENDOR_MAX should not point
              in the middle of the valid enum values.

Martin

---
 gcc/common/config/i386/i386-cpuinfo.h | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gcc/common/config/i386/i386-cpuinfo.h b/gcc/common/config/i386/i386-cpuinfo.h
index 9893fc422bc..586a1a2d0f6 100644
--- a/gcc/common/config/i386/i386-cpuinfo.h
+++ b/gcc/common/config/i386/i386-cpuinfo.h
@@ -34,8 +34,10 @@ enum processor_vendor
   VENDOR_CENTAUR,
   VENDOR_CYRIX,
   VENDOR_NSC,
+
+  /* Maximum values must be at the end of this enum.  */
+  VENDOR_MAX,
   BUILTIN_VENDOR_MAX = VENDOR_OTHER,
-  VENDOR_MAX
 };
 
 /* Any new types or subtypes have to be inserted at the end. */
-- 
2.38.0


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2022-10-24 18:24 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-24 18:24 [PATCH (pushed)] x86: fix VENDOR_MAX enum value Martin Liška

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).