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/102058] 450.soplex regressed on x86_64 with -Ofast -march=generic (by 8-15%) Date: Wed, 25 Aug 2021 10:00:10 +0000 [thread overview] Message-ID: <bug-102058-4-znLmUqHye4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102058-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102058 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Created attachment 51355 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51355&action=edit patch to add --param vect-emulated-gather for debugging When using attached patch then 0 vs. 1 on zen2 indeed reproduces Estimated Estimated Base Base Base Peak Peak Peak Benchmarks Ref. Run Time Ratio Ref. Run Time Ratio -------------- ------ --------- --------- ------ --------- --------- 450.soplex 8340 120 69.5 * 8340 136 61.4 * trying to nail it down now.
next prev parent reply other threads:[~2021-08-25 10:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-25 8:41 [Bug tree-optimization/102058] New: " jamborm at gcc dot gnu.org 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 [this message] 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 2024-06-20 8:57 ` [Bug tree-optimization/102058] [12/13/14/15 " 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-znLmUqHye4@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).