From: Henri Cloetens <henri.cloetens@blueice.be>
To: stefan@franke.ms, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: AW: How to recognize registers after reload ?.
Date: Fri, 23 Oct 2020 09:56:04 +0200 [thread overview]
Message-ID: <443b2c1b-4b1f-0616-0fc4-198c38e45ba8@blueice.be> (raw)
In-Reply-To: <0cd001d6a90f$0fd96f80$2f8c4e80$@bebbosoft.de>
Thank you Stefan,
How do you mean too narrow ?.
Can you be more specific ?, how should I change it, so that 'combine'
does not see non-exisiting patterns, while 'reload' is able to move
to stack, even when declaring a stack variable as a register ?.
Best Regards,
Henri
> Henri,
>
> it seems your define_expand for movsi is too narrow. It should accept all mandatory forms. The distinction - to register/memory - should be done in movsi itself. There is also no need for a database to distinguish.
>
> Regards
>
> Stefan
>
>
next prev parent reply other threads:[~2020-10-23 7:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 8:02 Henri Cloetens
2020-10-22 21:30 ` Jeff Law
2020-10-22 22:24 ` Segher Boessenkool
2020-10-22 23:47 ` Jeff Law
2020-10-23 7:28 ` Henri Cloetens
2020-10-23 7:35 ` AW: " Stefan Franke
2020-10-23 7:56 ` Henri Cloetens [this message]
2020-10-23 10:20 ` Segher Boessenkool
2020-10-23 11:38 ` Henri Cloetens
2020-10-23 10:02 ` Segher Boessenkool
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=443b2c1b-4b1f-0616-0fc4-198c38e45ba8@blueice.be \
--to=henri.cloetens@blueice.be \
--cc=gcc-help@gcc.gnu.org \
--cc=stefan@franke.ms \
/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).