public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110088] [avr] Improve operation with const on l-reg after move from d-reg Date: Fri, 02 Jun 2023 10:42:53 +0000 [thread overview] Message-ID: <bug-110088-4-yutFGXvYha@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110088-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110088 --- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Georg-Johann Lay <gjl@gcc.gnu.org>: https://gcc.gnu.org/g:7bf89a919fdab9e18b7ad3efaa1a79f1d7520ddf commit r14-1492-g7bf89a919fdab9e18b7ad3efaa1a79f1d7520ddf Author: Georg-Johann Lay <avr@gjlay.de> Date: Fri Jun 2 12:41:07 2023 +0200 target/110088: Improve operation of l-reg with const after move from d-reg. After reload, there may be sequences like lreg = dreg lreg = lreg <op> const with an LD_REGS dreg, non-LD_REGS lreg, and <op> in PLUS, IOR, AND. If dreg dies after the first insn, it is possible to use dreg = dreg <op> const lreg = dreg instead which is more efficient. gcc/ PR target/110088 * config/avr/avr.md: Add an RTL peephole to optimize operations on non-LD_REGS after a move from LD_REGS. (piaop): New code iterator.
next prev parent reply other threads:[~2023-06-02 10:42 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-02 10:26 [Bug target/110088] New: " 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 [this message] 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
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-110088-4-yutFGXvYha@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).