public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/110088] New: [avr] Improve operation with const on l-reg after move from d-reg
@ 2023-06-02 10:26 gjl at gcc dot gnu.org
  2023-06-02 10:27 ` [Bug target/110088] " gjl at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: gjl at gcc dot gnu.org @ 2023-06-02 10:26 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110088

            Bug ID: 110088
           Summary: [avr] Improve operation with const on l-reg after move
                    from d-reg
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gjl at gcc dot gnu.org
  Target Milestone: ---

The register allocator might generate code that moves a value from a d-reg to
an l-reg, and then performs operation like PLUS, IOR, AND with a constant.  So
we have a sequence like:

lreg = dreg
lreg = lreg <op> const

This is expensive because lreg cannot handle const and needs a QI scratch to
load bytes of const.  Instead, if dreg dies after the first insn, better code
is:

dreg = dreg <op> const
lreg = dreg

An RTL peephole can catch this.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2023-06-02 11:03 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-02 10:26 [Bug target/110088] New: [avr] Improve operation with const on l-reg after move from d-reg gjl at gcc dot gnu.org
2023-06-02 10:27 ` [Bug target/110088] " gjl at gcc dot gnu.org
2023-06-02 10:42 ` cvs-commit at gcc dot gnu.org
2023-06-02 10:55 ` cvs-commit at gcc dot gnu.org
2023-06-02 11:02 ` cvs-commit at gcc dot gnu.org
2023-06-02 11:03 ` gjl at gcc dot gnu.org

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).