public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64795] [5 regression] too many memory references for `lea' Date: Mon, 26 Jan 2015 18:50:00 -0000 [thread overview] Message-ID: <bug-64795-4-6F6abuW7kF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64795-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64795 --- Comment #3 from uros at gcc dot gnu.org --- Author: uros Date: Mon Jan 26 18:49:21 2015 New Revision: 220128 URL: https://gcc.gnu.org/viewcvs?rev=220128&root=gcc&view=rev Log: PR target/64795 * config/i386/i386.md (*movdi_internal): Also check operand 0 to determine TYPE_LEA operand. (*movsi_internal): Ditto. Modified: trunk/gcc/ChangeLog trunk/gcc/config/i386/i386.md
next prev parent reply other threads:[~2015-01-26 18:50 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-26 12:10 [Bug lto/64795] New: [5.0 regression x86_64] " dimhen at gmail dot com 2015-01-26 12:15 ` [Bug lto/64795] " dimhen at gmail dot com 2015-01-26 12:22 ` [Bug target/64795] " rguenth at gcc dot gnu.org 2015-01-26 18:50 ` uros at gcc dot gnu.org [this message] 2015-01-26 20:13 ` [Bug target/64795] [5 regression] " uros at gcc dot gnu.org 2015-01-26 20:50 ` uros at gcc dot gnu.org 2015-01-26 20:51 ` 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-64795-4-6F6abuW7kF@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).