public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/47949] New: Missed optimization for -Os using xchg instead of mov.
@ 2011-03-02  5:30 svfuerst at gmail dot com
  2011-03-02 10:23 ` [Bug target/47949] " rguenth at gcc dot gnu.org
                   ` (5 more replies)
  0 siblings, 6 replies; 7+ messages in thread
From: svfuerst at gmail dot com @ 2011-03-02  5:30 UTC (permalink / raw)
  To: gcc-bugs

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

           Summary: Missed optimization for -Os using xchg instead of mov.
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: svfuerst@gmail.com
            Target: x86 / amd64


xchg %eax, reg is a one-byte instruction.  If reg is dead, this instruction
could replace the two-byte mov reg, %eax for a one-byte savings.

ie:

int foo(int x)
{
    return x;
}

currently compiles to

mov    %edi,%eax
retq

with -Os, whereas the following may be better:

xchg %eax, %edi
retq

(Similar cases exist with mov reg, %rax; mov reg, %ax; and mov reg, %al)

Note that xchg is slower than mov, so this is only an optimization when size is
more important than speed.


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

end of thread, other threads:[~2022-08-04 18:23 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-03-02  5:30 [Bug target/47949] New: Missed optimization for -Os using xchg instead of mov 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
2022-08-04 18:23 ` roger at nextmovesoftware dot com

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