public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/110093] [12/13/14 Regression][avr] Move frenzy leading to code bloat Date: Tue, 29 Aug 2023 17:15:32 +0000 [thread overview] Message-ID: <bug-110093-4-KtZIZ6XT8v@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110093-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110093 --- Comment #3 from Vladimir Makarov <vmakarov at gcc dot gnu.org> --- I worked on avr issues quite some time. And here is my findings. Before IRA we have start of BB2: ;; lr in 14 [r14] 15 [r15] 16 [r16] 17 [r17] 18 [r18] 19 [r19] 20 [r20] 21 [r21] 22 [r22] 23 [r23] 24 [r24] 25 [r25] 28 [r28] 32 [__SP_L__] 34 [argL] 44 45 46 33: r51:QI=r22:QI REG_DEAD r22:QI 34: r52:QI=r23:QI REG_DEAD r23:QI 35: r53:QI=r24:QI REG_DEAD r24:QI 36: r54:QI=r25:QI REG_DEAD r25:QI 37: r44:SI#0=r51:QI REG_DEAD r51:QI 38: r44:SI#1=r52:QI REG_DEAD r52:QI 39: r44:SI#2=r53:QI REG_DEAD r53:QI 40: r44:SI#3=r54:QI REG_DEAD r54:QI According GCC pseudo r44 conflicts with r51, r52 ... In reality it is not. I could modify BB live analysis in IRA although it is a lot of work. But there is a bigger problem. A lot of passes including IRA uses data-flow analysis framework for global life analysis and it does not work on subreg level. You can see that r44 still lives (lr in) at the beginning of BB2. DFA is not my responsibility but I can say modifying DFA this way is a huge project as it will affect a lot of targets. Instead, as AVR regs are very small, I propose to avoid the above RTL code by switching off subreg3 pass (or -fsplit-wide-types) for AVR by default as it was for gcc-8. There is still one minor problem: an additional reg-reg move generation for the test case in comparison with gcc-8. I'll try to fix it.
next prev parent reply other threads:[~2023-08-29 17:15 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-02 13:22 [Bug rtl-optimization/110093] New: " gjl at gcc dot gnu.org 2023-06-05 6:38 ` [Bug rtl-optimization/110093] " rguenth at gcc dot gnu.org 2023-06-13 10:18 ` gjl at gcc dot gnu.org 2023-08-22 14:25 ` gjl at gcc dot gnu.org 2023-08-22 14:25 ` gjl at gcc dot gnu.org 2023-08-29 17:15 ` vmakarov at gcc dot gnu.org [this message] 2023-08-30 8:16 ` gjl at gcc dot gnu.org 2023-08-30 14:04 ` vmakarov at gcc dot gnu.org 2024-03-08 15:35 ` law at gcc dot gnu.org 2024-06-20 9:12 ` [Bug rtl-optimization/110093] [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-110093-4-KtZIZ6XT8v@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).