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/47949] Missed optimization for -Os using xchg instead of mov.
Date: Wed, 03 Aug 2022 08:11:20 +0000	[thread overview]
Message-ID: <bug-47949-4-UtJd74cTLi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47949-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:fc6ef90173478521982e9df3831a06ea85b4f41e

commit r13-1945-gfc6ef90173478521982e9df3831a06ea85b4f41e
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Wed Aug 3 09:07:36 2022 +0100

    PR target/47949: Use xchg to move from/to AX_REG with -Oz on x86.

    This patch adds a peephole2 to i386.md to implement the suggestion in
    PR target/47949, of using xchg instead of mov for moving values to/from
    the %rax/%eax register, controlled by -Oz, as the xchg instruction is
    one byte shorter than the move it is replacing.

    The new test case is taken from the PR:
    int foo(int x) { return x; }

    where previously we'd generate:
    foo:    mov %edi,%eax  // 2 bytes
            ret

    but with this patch, using -Oz, we generate:
    foo:    xchg %eax,%edi  // 1 byte
            ret

    On the CSiBE benchmark, this saves a total of 10238 bytes (reducing
    the -Oz total from 3661796 bytes to 3651558 bytes, a 0.28% saving).

    Interestingly, some modern architectures (such as Zen 3) implement
    xchg using zero latency register renaming (just like mov), so in theory
    this transformation could be enabled when optimizing for speed, if
    benchmarking shows the improved code density produces consistently
    better performance.  However, this is architecture dependent, and
    there may be interactions using xchg (instead a single_set) in the
    late RTL passes (such as cprop_hardreg), so for now I've restricted
    this to -Oz.

    2022-08-03  Roger Sayle  <roger@nextmovesoftware.com>
                Uroš Bizjak  <ubizjak@gmail.com>

    gcc/ChangeLog
            PR target/47949
            * config/i386/i386.md (peephole2): New peephole2 to convert
            SWI48 moves to/from %rax/%eax where the src is dead to xchg,
            when optimizing for minimal size with -Oz.

    gcc/testsuite/ChangeLog
            PR target/47949
            * gcc.target/i386/pr47949.c: New test case.

  parent reply	other threads:[~2022-08-03  8:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02  5:30 [Bug target/47949] New: " svfuerst at gmail dot com
2011-03-02 10:23 ` [Bug target/47949] " rguenth at gcc dot gnu.org
2011-03-02 10:53 ` jakub at gcc dot gnu.org
2011-03-02 21:51 ` svfuerst at gmail dot com
2021-06-08  9:52 ` pinskia at gcc dot gnu.org
2022-08-03  8:11 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-04 18:23 ` roger at nextmovesoftware dot com

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-47949-4-UtJd74cTLi@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: link
Be 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).