public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roger at eyesopen dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/17236] inefficient code for long long multiply on x86 Date: Fri, 02 Feb 2007 00:17:00 -0000 [thread overview] Message-ID: <20070202001707.23057.qmail@sourceware.org> (raw) In-Reply-To: <bug-17236-1008@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from roger at eyesopen dot com 2007-02-02 00:17 ------- It looks like Ian's recent subreg lowering pass patch has improved code generation on this testcase. Previously, we'd spill three integer registers to the stack for "LLM", we're now down to two. [A significant improvement from the five we spilled when this bug was reported] Before: LLM: subl $12, %esp movl %ebx, (%esp) movl 28(%esp), %edx movl 20(%esp), %ebx movl 16(%esp), %ecx movl 24(%esp), %eax movl %esi, 4(%esp) movl %edx, %esi movl %edi, 8(%esp) movl %ebx, %edi movl (%esp), %ebx imull %ecx, %esi imull %eax, %edi mull %ecx addl %edi, %esi movl 8(%esp), %edi leal (%esi,%edx), %edx movl 4(%esp), %esi addl $12, %esp ret After: LLM: subl $8, %esp movl %ebx, (%esp) movl 20(%esp), %eax movl %esi, 4(%esp) movl 24(%esp), %ecx movl 12(%esp), %esi movl 16(%esp), %ebx imull %esi, %ecx imull %eax, %ebx mull %esi movl 4(%esp), %esi addl %ebx, %ecx movl (%esp), %ebx addl $8, %esp leal (%ecx,%edx), %edx ret -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17236
next parent reply other threads:[~2007-02-02 0:17 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-17236-1008@http.gcc.gnu.org/bugzilla/> 2007-02-02 0:17 ` roger at eyesopen dot com [this message] 2007-11-23 20:48 ` steven at gcc dot gnu dot org 2007-12-18 7:43 ` bonzini at gnu dot org 2007-12-18 7:53 ` bonzini at gnu dot org 2007-12-18 8:05 ` bonzini at gnu dot org 2007-12-18 8:10 ` ebotcazou at gcc dot gnu dot org 2007-12-18 13:48 ` ubizjak at gmail dot com 2007-12-18 16:02 ` bonzini at gnu dot org 2007-12-18 16:39 ` jakub at gcc dot gnu dot org 2007-12-18 16:51 ` bonzini at gnu dot org 2007-12-18 18:20 ` ubizjak at gmail dot com 2007-12-18 18:33 ` ubizjak at gmail dot com 2007-12-19 9:49 ` bonzini at gnu dot org 2007-12-19 12:11 ` ubizjak at gmail dot com 2007-12-19 12:14 ` bonzini at gnu dot org 2007-12-19 12:32 ` bonzini at gnu dot org 2007-12-19 12:43 ` bonzini at gnu dot org 2007-12-19 13:12 ` ubizjak at gmail dot com 2007-12-19 13:36 ` bonzini at gnu dot org 2007-12-19 13:49 ` steven at gcc dot gnu dot org 2007-12-19 13:50 ` bonzini at gnu dot org 2007-12-19 13:54 ` bonzini at gnu dot org 2007-12-20 13:53 ` bonzini at gnu dot org 2007-12-20 14:16 ` bonzini at gnu dot org 2008-03-07 8:27 ` bonzini at gnu dot org 2008-03-07 8:42 ` bonzini at gnu dot org 2008-09-06 16:12 ` ubizjak at gmail dot com 2008-09-06 16:19 ` ubizjak at gmail dot com 2008-09-06 16:20 ` ubizjak at gmail dot com 2004-08-30 5:50 [Bug rtl-optimization/17236] New: " dann at godzilla dot ics dot uci dot edu 2004-10-06 23:27 ` [Bug rtl-optimization/17236] " giovannibajo at libero dot it 2005-03-14 18:24 ` cvs-commit at gcc dot gnu dot org 2005-03-15 10:05 ` giovannibajo at libero dot it 2005-03-15 10:07 ` giovannibajo at libero dot it
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=20070202001707.23057.qmail@sourceware.org \ --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).