From: Julian Brown <julian@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: Re: Multiple types of load/store: how to create .md rules?
Date: Wed, 4 May 2022 11:07:10 +0100 [thread overview]
Message-ID: <20220504110710.3c4936cc@squid.athome> (raw)
In-Reply-To: <0f574adfe4c15da62238eeba1c939414a4a23198.camel@tantosonline.com>
On Mon, 02 May 2022 19:10:41 -0700
Andras Tantos <andras@tantosonline.com> wrote:
> To a previous problem I've asked, Andrew Pinski replied that I should
> merge all *movsi patterns into a single one to avoid (in that case)
> strange deletions in the generated assembly. Is that possible here? It
> appears to me that I would need the ability to differentiate the
> different patterns using constraints, but is there a way to define
> custom versions of the 'm' pattern? I didn't find anything on that in
> the documentation. Did I miss something?
Check "define_memory_constraint" in existing ports, i.e.:
https://gcc.gnu.org/onlinedocs/gccint/Define-Constraints.html#index-define_005fmemory_005fconstraint
HTH,
Julian
prev parent reply other threads:[~2022-05-04 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 2:10 Andras Tantos
2022-05-04 10:07 ` Julian Brown [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=20220504110710.3c4936cc@squid.athome \
--to=julian@codesourcery.com \
--cc=gcc@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: 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).