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/84201] 549.fotonik3d_r from SPEC2017 fails verification with recent Intel and AMD CPUs Date: Thu, 17 Feb 2022 13:55:52 +0000 [thread overview] Message-ID: <bug-84201-4-unhgtCXZuB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-84201-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84201 --- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> --- One option is to introduce a less invasive optimization option to avoid the undesirable vectorization. For example -fno-vectorize-fp-inductions noting this particular loop is a floating-point induction. Usually those tend not to be performance critical. More general -f[no-]vectorize-{in,re}ductions[={fp,int}] would be possible as well.
next prev parent reply other threads:[~2022-02-17 13:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-84201-4@http.gcc.gnu.org/bugzilla/> 2020-09-17 20:46 ` mailboxnotfound at yahoo dot com 2022-02-17 13:55 ` rguenth at gcc dot gnu.org [this message] 2022-02-17 15:48 ` jamborm at gcc dot gnu.org 2022-02-18 8:22 ` rguenth at gcc dot gnu.org 2022-03-08 11:12 ` rguenth at gcc dot gnu.org 2022-03-08 11:53 ` rguenth at gcc dot gnu.org 2022-03-08 14:58 ` cvs-commit at gcc dot gnu.org 2022-03-08 15:01 ` rguenth at gcc dot gnu.org 2024-01-24 16:07 ` law 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-84201-4-unhgtCXZuB@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).