public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin 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: Mon, 24 Oct 2022 20:30:30 +0000 [thread overview] Message-ID: <bug-107364-4-KMkA0xnJtX@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 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hjl at gcc dot gnu.org --- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> --- ... > That means that all CENTAUR/CYRIX/NSC were broken since gcc 10 and nobody > noticed until me ?? That sounds very unlikely, does it not ? Yes, you are the first one who noticed! > > (I dont even know what NSC is) > > I'm not sure, but the "wrong" commit seems to be the very large > > https://github.com/gcc-mirror/gcc/commit/ > 1890f2f0e210ef515c39728c54151372d36dd187 Yep, I know about this commit. I suspect g:6c35d16a3925958b3a22426de0cb8e04f654b6dd where e.g. sse detection is unified: - has_sse = edx & bit_SSE; and rather: + else if (has_feature (FEATURE_SSE2) is used. And then in g:792317cc777123b9cac8fc9a70fc85b01a3d7a0f newly added get_available_features which does the ISA features detection is called only for AMD and Intel CPUs :/
next prev parent reply other threads:[~2022-10-24 20:30 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 [this message] 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 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-KMkA0xnJtX@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: linkBe 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).