public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112697] [14 Regression] 30-40% exec time regression of 433.milc on zen2 since r14-4972-g8aa47713701b1f Date: Fri, 01 Dec 2023 15:37:03 +0000 [thread overview] Message-ID: <bug-112697-4-bR7h7IX0KC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112697-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112697 --- Comment #8 from Alexander Monakov <amonakov at gcc dot gnu.org> --- Thanks, I can reproduce it. It is pretty tricky though. For instance, just swapping the mov and the compare is enough to make it fast: --- d.out.ltrans0.ltrans.slow.s 2023-12-01 18:32:54.255841611 +0300 +++ d.out.ltrans0.ltrans.fast.s 2023-12-01 18:32:20.318668991 +0300 @@ -743,8 +743,8 @@ add_force_to_mom: .p2align 4,,10 .p2align 3 .L58: - cmpb $1, -680(%r11,%r12) movapd %xmm5, %xmm7 + cmpb $1, -680(%r11,%r12) jne .L54 xorpd %xmm6, %xmm7 .L54:
next prev parent reply other threads:[~2023-12-01 15:37 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-24 9:03 [Bug middle-end/112697] New: [14 Regression] 30-40% exec time regression of 433.milc on zen2 fkastl at suse dot cz 2023-11-24 9:07 ` [Bug middle-end/112697] " fkastl at suse dot cz 2023-11-24 9:51 ` rguenth at gcc dot gnu.org 2023-11-24 17:45 ` jamborm at gcc dot gnu.org 2023-11-24 17:52 ` [Bug middle-end/112697] [14 Regression] 30-40% exec time regression of 433.milc on zen2 since r14-4972-g8aa47713701b1f sjames at gcc dot gnu.org 2023-11-27 11:58 ` amonakov at gcc dot gnu.org 2023-11-29 13:52 ` jamborm at gcc dot gnu.org 2023-11-29 13:53 ` jamborm at gcc dot gnu.org 2023-12-01 15:37 ` amonakov at gcc dot gnu.org [this message] 2023-12-01 16:00 ` amonakov at gcc dot gnu.org 2024-03-07 21:01 ` law at gcc dot gnu.org 2024-03-21 9:45 ` pheeck at gcc dot gnu.org 2024-03-22 12:47 ` 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-112697-4-bR7h7IX0KC@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).