From: Richard Sandiford <richard.sandiford@arm.com>
To: Hongtao Liu via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Vladimir Makarov <vmakarov@redhat.com>,
Hongtao Liu <crazylht@gmail.com>,
dcb314@hotmail.com
Subject: Re: [PATCH][PR target/97540] Don't extract memory from operand for normal memory constraint.
Date: Thu, 29 Oct 2020 17:03:22 +0000 [thread overview]
Message-ID: <mpt8sbp9d7p.fsf@arm.com> (raw)
In-Reply-To: <CAMZc-bxp-7E0Epv4_90yLYNeJvMGBVSptM-vJH=PKcSkGJqcbw@mail.gmail.com> (Hongtao Liu via Gcc-patches's message of "Thu, 29 Oct 2020 13:33:11 +0800")
Hongtao Liu via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
> On Tue, Oct 27, 2020 at 7:13 PM Richard Sandiford
> <richard.sandiford@arm.com> wrote:
>>
>> Hongtao Liu via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
>> > Hi:
>> > For inline asm, there could be an operand like (not (mem:)), it's
>> > not a valid operand for normal memory constraint.
>> > Bootstrap is ok, regression test is ok for make check
>> > RUNTESTFLAGS="--target_board='unix{-m32,}'"
>> >
>> > gcc/ChangeLog
>> > PR target/97540
>> > * ira.c: (ira_setup_alts): Extract memory from operand only
>> > for special memory constraint.
>> > * recog.c (asm_operand_ok): Ditto.
>> > * lra-constraints.c (process_alt_operands): MEM_P is
>> > required for normal memory constraint.
>> >
>> > gcc/testsuite/ChangeLog
>> > * gcc.target/i386/pr97540.c: New test.
>>
>> Sorry to stick my oar in, but I think we should reconsider the
>> bcst_mem_operand approach. It seems like these patches (and the
>> previous one) are fighting against the principle that operands
>> cannot be arbitrary expressions.
>>
>> This kind of thing was attempted long ago (even before my time!)
>> for SIGN_EXTEND on MIPS. It ended up causing more problems than
>> it solved and in the end it had to be taken out. I'm worried that
>> we might end up going through the same cycle again.
>>
>
> Could you provide the thread link for the issue of SIGN_EXTEND on
> MIPS, then I can take a look to see if it's exactly the same issue as
> mine.
I couldn't find anything, sorry. The patch that finally removed
the MIPS handling was:
https://gcc.gnu.org/pipermail/gcc-patches/2002-October/088178.html
I know there was some discussion about the problems around then,
but some of it might have been private rather than on-list.
I can't remember the details now.
Thanks,
Richard
next prev parent reply other threads:[~2020-10-29 17:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 6:53 Hongtao Liu
2020-10-27 11:13 ` Richard Sandiford
2020-10-28 1:32 ` Hongtao Liu
2020-10-28 18:46 ` Richard Sandiford
2020-10-29 1:20 ` Hongtao Liu
2020-10-29 17:00 ` Richard Sandiford
2020-11-02 7:12 ` Hongtao Liu
2020-11-02 19:03 ` Richard Sandiford
2020-10-29 5:33 ` Hongtao Liu
2020-10-29 17:03 ` Richard Sandiford [this message]
2020-10-31 17:16 ` Hans-Peter Nilsson
2020-10-29 11:01 ` Jakub Jelinek
2020-10-29 17:16 ` Richard Sandiford
2020-11-02 19:40 ` Vladimir Makarov
2020-11-03 13:51 ` Richard Sandiford
2020-11-04 5:14 ` Hongtao Liu
2020-11-04 10:19 ` Richard Sandiford
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=mpt8sbp9d7p.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=crazylht@gmail.com \
--cc=dcb314@hotmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@redhat.com \
/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).