public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104683] -march=haswell generates invalid instructions on Celeron Haswell CPUs Date: Fri, 25 Feb 2022 10:32:20 +0000 [thread overview] Message-ID: <bug-104683-4-4tzUZ3Q1Ci@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104683-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104683 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Same for -march=broadwell and -march=skylake (G3900) btw (just browsing Intel Ark database). Can't figure what's the "celeron/pentium" successor to the skylake family is to check if even newer SKUs are affected. As said changing -march=skylake to not include AVX2 would be a bad idea, adding -march=skylake-noavx might work but then nobody would use that so I'm not sure what's the point. But again - fun ... let's see if Intel manages to fuse of AVX for some Alderlake SKUs ...
next prev parent reply other threads:[~2022-02-25 10:32 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-25 2:22 [Bug other/104683] New: " pc-gcc22 at crowcastle dot net 2022-02-25 8:27 ` [Bug target/104683] " rguenth at gcc dot gnu.org 2022-02-25 10:32 ` rguenth at gcc dot gnu.org [this message] 2022-02-25 10:38 ` rguenth at gcc dot gnu.org 2022-02-25 14:37 ` pc-gcc22 at crowcastle dot net
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-104683-4-4tzUZ3Q1Ci@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).