public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vda.linux at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/64907] New: Suboptimal code (saving rbx on stack in order to save another reg in rbx) Date: Mon, 02 Feb 2015 18:36:00 -0000 [thread overview] Message-ID: <bug-64907-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64907 Bug ID: 64907 Summary: Suboptimal code (saving rbx on stack in order to save another reg in rbx) Product: gcc Version: 4.7.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: vda.linux at googlemail dot com void put_16bit(unsigned short v); void put_32bit(unsigned v) { put_16bit(v); put_16bit(v >> 16); } With gcc 4.7.2 the above compiles to the following assembly: put_32bit: pushq %rbx movl %edi, %ebx andl $65535, %edi call put_16bit movl %ebx, %edi popq %rbx shrl $16, %edi jmp put_16bit Code saves %rbx on stack only in order to save %edi to %ebx. A simpler alternative is to just save %rdi on stack: put_32bit: pushq %rdi andl $65535, %edi call put_16bit popq %rdi shrl $16, %edi jmp put_16bit
next reply other threads:[~2015-02-02 18:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-02 18:36 vda.linux at googlemail dot com [this message] 2015-02-02 19:09 ` [Bug rtl-optimization/64907] " hjl.tools at gmail 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-64907-4@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).