From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "ams@codesourcery.com" <ams@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 00/25] AMD GCN Port
Date: Mon, 17 Sep 2018 10:52:00 -0000 [thread overview]
Message-ID: <VI1PR0701MB28623E206481BE935E29DFF4E41E0@VI1PR0701MB2862.eurprd07.prod.outlook.com> (raw)
<ams@codesourcery.com> writes:
> Given a pattern with a number of operands:
>
> (match_operand 0 "" "=&v")
> (match_operand 1 "" " v0")
> (match_operand 2 "" " v0")
> (match_operand 3 "" " v0")
>
> GCC will currently increment "reject" once, for operand 0, and then decrement
> it once for each of the other operands, ending with reject == -2 and an
> assertion failure. If there's a conflict then it might try to decrement reject
> yet again.
>
> Incidentally, what these patterns are trying to achieve is an allocation in
> which operand 0 may match one of the other operands, but may not partially
> overlap any of them. Ideally there'd be a better way to do this.
I have seen something similar in the arm.md:
where this allocation problem is solved differently:
(define_insn_and_split "*arm_subdi3"
[(set (match_operand:DI 0 "arm_general_register_operand" "=&r,&r,&r")
(minus:DI (match_operand:DI 1 "arm_general_register_operand" "0,r,0")
(match_operand:DI 2 "arm_general_register_operand" "r,0,0")))
DI registers are always consecutive register pairs,
but they should not partially overlap.
They solve that by using alternatives.
Bernd.
next reply other threads:[~2018-09-17 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 10:52 Bernd Edlinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-05 11:49 ams
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=VI1PR0701MB28623E206481BE935E29DFF4E41E0@VI1PR0701MB2862.eurprd07.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=ams@codesourcery.com \
--cc=gcc-patches@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).