public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107364] [10/11/12 Regression] ICE on Via Nehemiah with --march=native
Date: Tue, 25 Oct 2022 03:56:54 +0000	[thread overview]
Message-ID: <bug-107364-4-5c72NGJOX4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107364-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107364

--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:

https://gcc.gnu.org/g:4db0753959dc7aeff567c689be6c4eb611aea8ee

commit r12-8863-g4db0753959dc7aeff567c689be6c4eb611aea8ee
Author: Martin Liska <mliska@suse.cz>
Date:   Mon Oct 24 15:34:39 2022 +0200

    x86: fix VENDOR_MAX enum value

            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.

    (cherry picked from commit f751bf4c5d1aaa1aacfcbdec62881c5ea1175dfb)

  parent reply	other threads:[~2022-10-25  3:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-23 10:47 [Bug c/107364] New: " orzel at freehackers dot org
2022-10-23 23:58 ` [Bug target/107364] [10/11/12/13 Regression] " pinskia at gcc dot gnu.org
2022-10-24  8:02 ` marxin at gcc dot gnu.org
2022-10-24 13:00 ` orzel at freehackers dot org
2022-10-24 13:36 ` marxin at gcc dot gnu.org
2022-10-24 13:40 ` marxin at gcc dot gnu.org
2022-10-24 18:26 ` cvs-commit at gcc dot gnu.org
2022-10-24 18:27 ` [Bug target/107364] [10/11/12 " marxin at gcc dot gnu.org
2022-10-24 19:52 ` orzel at freehackers dot org
2022-10-24 20:18 ` orzel at freehackers dot org
2022-10-24 20:30 ` marxin at gcc dot gnu.org
2022-10-24 20:38 ` hjl.tools at gmail dot com
2022-10-24 20:46 ` orzel at freehackers dot org
2022-10-25  3:55 ` cvs-commit at gcc dot gnu.org
2022-10-25  3:56 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-25  4:18 ` cvs-commit at gcc dot gnu.org
2022-10-25  4:24 ` cvs-commit at gcc dot gnu.org
2022-10-25  4:24 ` cvs-commit at gcc dot gnu.org
2022-10-25  4:25 ` cvs-commit at gcc dot gnu.org
2022-10-25  4:29 ` marxin at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107364-4-5c72NGJOX4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).