From: Richard Sandiford <richard.sandiford@linaro.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches@gcc.gnu.org, patches@linaro.org
Subject: Re: Recording predicate information in all rtl gen* programs
Date: Tue, 12 Apr 2011 15:01:00 -0000 [thread overview]
Message-ID: <g462qjecpk.fsf@linaro.org> (raw)
In-Reply-To: <BANLkTinqHoNBe7BrxQ9VCk0qikm+aW0+-g@mail.gmail.com> (H. J. Lu's message of "Tue, 12 Apr 2011 07:07:09 -0700")
"H.J. Lu" <hjl.tools@gmail.com> writes:
> I think your patch caused:
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48573
Sorry, this didn't show up on pure x86_64. It was caused by the
optabs.c patch rather than this one. I've reverted it for now.
One fix would be:
/* If the operand is a memory, try forcing the address into a register. */
if (MEM_P (op->value)
&& GET_RTX_CLASS (GET_CODE (XEXP (op->value, 0))) != RTX_AUTOINC
&& insn_data[(int) icode].operand[opno].allows_mem)
I think all other addresses really can be forced into registers.
Richard
prev parent reply other threads:[~2011-04-12 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 12:29 Richard Sandiford
2011-04-12 12:46 ` Bernd Schmidt
2011-04-12 14:07 ` H.J. Lu
2011-04-12 15:01 ` Richard Sandiford [this message]
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=g462qjecpk.fsf@linaro.org \
--to=richard.sandiford@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=patches@linaro.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: link
Be 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).