public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/50603] [x32] Unnecessary lea Date: Mon, 03 Oct 2011 20:58:00 -0000 [thread overview] Message-ID: <bug-50603-4-FkPTKZKeON@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50603-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50603 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |UNCONFIRMED Ever Confirmed|1 |0 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> 2011-10-03 20:57:53 UTC --- I am testing this patch: diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c index 7e89dbd..612fcd2 100644 --- a/gcc/config/i386/i386.c +++ b/gcc/config/i386/i386.c @@ -15713,6 +15713,16 @@ ix86_fixup_binary_operands (enum rtx_code code, enum ma chine_mode mode, else src2 = force_reg (mode, src2); } + else + { + /* Improve address combine in x32 mode. */ + if (TARGET_X32 + && code == PLUS + && !MEM_P (dst) + && !MEM_P (src1) + && MEM_P (src2) ) + src2 = force_reg (mode, src2); + } /* If the destination is memory, and we do not have matching source operands, do things in registers. */
next prev parent reply other threads:[~2011-10-03 20:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-03 17:33 [Bug target/50603] New: " hjl.tools at gmail dot com 2011-10-03 19:13 ` [Bug target/50603] " ubizjak at gmail dot com 2011-10-03 20:58 ` hjl.tools at gmail dot com [this message] 2011-10-06 19:01 ` hjl.tools at gmail dot com 2011-10-06 19:19 ` hjl.tools at gmail dot com 2011-10-06 19:38 ` hjl.tools at gmail dot com 2011-10-06 19:44 ` hjl.tools at gmail dot com 2011-10-07 6:43 ` uros at gcc dot gnu.org 2011-10-09 9:30 ` ubizjak 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-50603-4-FkPTKZKeON@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).