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 tree-optimization/113833] 435.gromacs fails verification on with -Ofast -march={cascadelake,icelake-server} and PGO after r14-7272-g57f611604e8bab
Date: Fri, 09 Feb 2024 06:52:23 +0000 [thread overview]
Message-ID: <bug-113833-4-YnKuIe6HxA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113833-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113833
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I suspect the issue would pop up with -Ofast -fno-vect-cost-model for any
sub-architecture. The patch referenced just adjusts costs for doing BB
vectorization (and there's reductions there as well). It might be interesting
to offer more high-level knobs to tune for vectorization, say
-fno-vect-bb-reduction or -fforce-in-order-bb-reduction-vectorization.
A compare before/after the patch of -fopt-info-vec output might show the few
cases that are affected by the patch.
next prev parent reply other threads:[~2024-02-09 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 16:37 [Bug tree-optimization/113833] New: " jamborm at gcc dot gnu.org
2024-02-09 0:55 ` [Bug tree-optimization/113833] " pinskia at gcc dot gnu.org
2024-02-09 1:01 ` pinskia at gcc dot gnu.org
2024-02-09 6:52 ` rguenth at gcc dot gnu.org [this message]
2024-02-12 12:57 ` jamborm at gcc dot gnu.org
2024-02-25 11:13 ` pheeck 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-113833-4-YnKuIe6HxA@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).