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 rtl-optimization/102178] [12 Regression] SPECFP 2006 470.lbm regressions on AMD Zen CPUs after r12-897-gde56f95afaaa22 Date: Thu, 27 Jan 2022 10:32:00 +0000 [thread overview] Message-ID: <bug-102178-4-nvOkxZ6kZr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102178-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102178 --- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> --- So in .reload we have (with unpatched trunk) 401: NOTE_INSN_BASIC_BLOCK 6 462: ax:DF=[`*.LC0'] REG_EQUAL 9.850689999999999724167309977929107844829559326171875e-1 407: xmm2:DF=ax:DF 463: ax:DF=[`*.LC0'] REG_EQUAL 9.850689999999999724167309977929107844829559326171875e-1 408: xmm4:DF=ax:DF why??! We can load .LC0 into xmm4 directly. IRA sees 401: NOTE_INSN_BASIC_BLOCK 6 407: r118:DF=r482:DF 408: r119:DF=r482:DF now I cannot really decipher IRA or LRA dumps but my guess would be that inheritance (causing us to load from LC0) interferes badly with register class assignment? Changing pseudo 482 in operand 1 of insn 407 on equiv 9.850689999999999724167309977929107844829559326171875e-1 ... alt=21,overall=9,losers=1,rld_nregs=1 Choosing alt 21 in insn 407: (0) v (1) r {*movdf_internal} Creating newreg=525, assigning class GENERAL_REGS to r525 407: r118:DF=r525:DF Inserting insn reload before: 462: r525:DF=[`*.LC0'] REG_EQUAL 9.850689999999999724167309977929107844829559326171875e-1 we should have preferred alt 14 I think (0) v (1) m, but that has alt=14,overall=13,losers=1,rld_nregs=0 0 Spill pseudo into memory: reject+=3 Using memory insn operand 0: reject+=3 0 Non input pseudo reload: reject++ 1 Non-pseudo reload: reject+=2 1 Non input pseudo reload: reject++ alt=15,overall=28,losers=3 -- refuse 0 Costly set: reject++ alt=16: Bad operand -- refuse 0 Costly set: reject++ 1 Costly loser: reject++ 1 Non-pseudo reload: reject+=2 1 Non input pseudo reload: reject++ alt=17,overall=17,losers=2 -- refuse 0 Costly set: reject++ 1 Spill Non-pseudo into memory: reject+=3 Using memory insn operand 1: reject+=3 1 Non input pseudo reload: reject++ alt=18,overall=14,losers=1 -- refuse 0 Spill pseudo into memory: reject+=3 Using memory insn operand 0: reject+=3 0 Non input pseudo reload: reject++ 1 Costly loser: reject++ 1 Non-pseudo reload: reject+=2 1 Non input pseudo reload: reject++ alt=19,overall=29,losers=3 -- refuse 0 Non-prefered reload: reject+=600 0 Non input pseudo reload: reject++ alt=20,overall=607,losers=1 -- refuse 1 Non-pseudo reload: reject+=2 1 Non input pseudo reload: reject++ I'm not sure I can decipher the reasoning but I don't understand how it doesn't seem to anticipate the cost of reloading the GPR in the alternative it chooses? Vlad?
next prev parent reply other threads:[~2022-01-27 10:32 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-02 15:38 [Bug tree-optimization/102178] New: " jamborm at gcc dot gnu.org 2021-09-03 7:07 ` [Bug tree-optimization/102178] " marxin at gcc dot gnu.org 2021-09-06 6:40 ` rguenth at gcc dot gnu.org 2021-09-06 6:41 ` [Bug tree-optimization/102178] [12 Regression] " rguenth at gcc dot gnu.org 2021-09-07 2:46 ` luoxhu at gcc dot gnu.org 2021-09-08 14:06 ` jamborm at gcc dot gnu.org 2021-09-16 16:17 ` jamborm at gcc dot gnu.org 2022-01-20 10:20 ` rguenth at gcc dot gnu.org 2022-01-26 15:57 ` marxin at gcc dot gnu.org 2022-01-27 7:42 ` [Bug rtl-optimization/102178] " rguenth at gcc dot gnu.org 2022-01-27 7:55 ` rguenth at gcc dot gnu.org 2022-01-27 8:13 ` crazylht at gmail dot com 2022-01-27 8:18 ` crazylht at gmail dot com 2022-01-27 8:20 ` rguenth at gcc dot gnu.org 2022-01-27 9:34 ` rguenth at gcc dot gnu.org 2022-01-27 9:55 ` Jan Hubicka 2022-01-27 9:55 ` hubicka at kam dot mff.cuni.cz 2022-01-27 10:13 ` rguenth at gcc dot gnu.org 2022-01-27 10:14 ` rguenth at gcc dot gnu.org 2022-01-27 10:23 ` hubicka at kam dot mff.cuni.cz 2022-01-27 10:32 ` rguenth at gcc dot gnu.org [this message] 2022-01-27 11:18 ` rguenth at gcc dot gnu.org 2022-01-27 11:30 ` rguenther at suse dot de 2022-01-27 11:33 ` rguenther at suse dot de 2022-01-27 12:04 ` Jan Hubicka 2022-01-27 12:04 ` hubicka at kam dot mff.cuni.cz 2022-01-27 13:42 ` hjl.tools at gmail dot com 2022-01-27 14:24 ` rguenth at gcc dot gnu.org 2022-01-27 16:28 ` crazylht at gmail dot com 2022-01-27 16:36 ` crazylht at gmail dot com 2022-01-28 15:48 ` vmakarov at gcc dot gnu.org 2022-01-28 16:02 ` vmakarov at gcc dot gnu.org 2022-02-09 15:51 ` vmakarov at gcc dot gnu.org 2022-02-10 7:45 ` rguenth at gcc dot gnu.org 2022-02-10 15:17 ` vmakarov at gcc dot gnu.org 2022-04-11 13:04 ` rguenth at gcc dot gnu.org 2022-04-25 9:45 ` rguenth at gcc dot gnu.org 2022-04-25 12:52 ` rguenth at gcc dot gnu.org 2022-04-25 13:02 ` rguenth at gcc dot gnu.org 2022-04-25 13:09 ` rguenth at gcc dot gnu.org 2023-04-26 6:55 ` [Bug rtl-optimization/102178] [12/13/14 " rguenth at gcc dot gnu.org 2023-07-27 9:22 ` rguenth at gcc dot gnu.org 2024-05-21 9:10 ` [Bug rtl-optimization/102178] [12/13/14/15 " jakub 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-102178-4-nvOkxZ6kZr@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).