public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102058] New: 450.soplex regressed on x86_64 with -Ofast -march=generic (by 8-15%)
Date: Wed, 25 Aug 2021 08:41:49 +0000 [thread overview]
Message-ID: <bug-102058-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102058
Bug ID: 102058
Summary: 450.soplex regressed on x86_64 with -Ofast
-march=generic (by 8-15%)
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jamborm at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
All three LNT x86_64 testers have experienced a regression when
running SPECFP 2006 benchmark 450.soplex compiled with -Ofast
-march=generic (as opposed to -march=native builds which seem not to
be affected).
A znver2 machine regressed by 15%:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=414.150.0&plot.1=300.150.0&
A znver1 machine regressed by 8%:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=451.150.0&plot.1=27.150.0&
An Intel Kabylake machine regressed by 9%:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=429.150.0&plot.1=25.150.0&
I have bisected the regression (on another znver2 machine) to revision
r12-2733-g31855ba6b16:
31855ba6b16cd138d7484076a08cd40d609654b8 is the first bad commit
commit 31855ba6b16cd138d7484076a08cd40d609654b8
Author: Richard Biener <rguenther@suse.de>
Date: Thu Jul 29 14:14:48 2021 +0200
Add emulated gather capability to the vectorizer
This adds a gather vectorization capability to the vectorizer
without target support by decomposing the offset vector, doing
sclar loads and then building a vector from the result. This
is aimed mainly at cases where vectorizing the rest of the loop
offsets the cost of vectorizing the gather.
[...]
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
next reply other threads:[~2021-08-25 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 8:41 jamborm at gcc dot gnu.org [this message]
2021-08-25 9:56 ` [Bug tree-optimization/102058] " marxin at gcc dot gnu.org
2021-08-25 10:00 ` rguenth at gcc dot gnu.org
2021-08-26 9:59 ` rguenth at gcc dot gnu.org
2021-10-29 13:05 ` [Bug tree-optimization/102058] [12 regression] " hubicka at gcc dot gnu.org
2021-11-02 6:52 ` rguenth at gcc dot gnu.org
2022-01-20 10:33 ` rguenth at gcc dot gnu.org
2022-02-10 10:18 ` rguenth at gcc dot gnu.org
2022-05-06 8:30 ` [Bug tree-optimization/102058] [12/13 " jakub at gcc dot gnu.org
2022-07-26 13:30 ` rguenth at gcc dot gnu.org
2023-05-08 12:22 ` [Bug tree-optimization/102058] [12/13/14 " rguenth 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-102058-4@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).