From: "Koning, Paul" <Paul.Koning@dell.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Always enable LRA
Date: Fri, 14 Oct 2022 12:37:41 +0000 [thread overview]
Message-ID: <7C52148F-A6D1-475F-B19D-2C340770B8EC@dell.com> (raw)
In-Reply-To: <40062fc8-42d4-40a7-cb53-250af8c98b89@gmail.com>
> On Oct 13, 2022, at 9:07 PM, Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>
>
> On 10/13/22 17:56, Segher Boessenkool wrote:
>>
>> h8300 fails during GCC build:
>> /home/segher/src/gcc/libgcc/unwind.inc: In function '_Unwind_SjLj_RaiseException':
>> /home/segher/src/gcc/libgcc/unwind.inc:141:1: error: could not split insn
>> 141 | }
>> | ^
>> (insn 69 256 327 (set (mem/f:SI (pre_dec:SI (reg/f:SI 7 sp)) [12 S4 A32])
>> (reg/f:SI 7 sp)) "/home/segher/src/gcc/libgcc/unwind.inc":118:12 19 {*movsi}
>> (expr_list:REG_ARGS_SIZE (const_int 4 [0x4])
>> (nil)))
>> during RTL pass: final
>> which looks like a backend bug, I don't see a pattern that could split
>> this (without needing an extra clobber)?
>
> I'm aware of this -- its invalid RTL:
>
> Uses of the register outside of an address are not permitted within the
> same insn as a use in an embedded side effect expression because such
> insns behave differently on different machines and hence must be treated
> as ambiguous and disallowed.
I had a bit of a fight with this sort of thing in pdp11, where in fact such operations are executed differently on different machine models. The solution I picked is to create two sets of machine-specific constraint codes, one for "register N" and the other for "autoinc/dec of any register other than N" and pairing those. (You can see this in pdp11.md, the mov<mode> definition.)
But the pdp11 case is actually not as restrictive as the rule you mentioned. The problem case is register N source, autoinc/dec rN destination. The opposite case, which we see here -- autoinc/dec Rn source, Rn destination -- is just fine. Perhaps not all that important, but the ISA definition does not object to it. So I'm not sure why there would be a general rule that says it's considered ambiguous when the target machine architecture says it is not.
paul
next prev parent reply other threads:[~2022-10-14 12:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 23:56 Segher Boessenkool
2022-10-14 0:36 ` Koning, Paul
2022-10-14 16:18 ` Segher Boessenkool
2022-10-14 16:48 ` Koning, Paul
2022-10-14 1:07 ` Jeff Law
2022-10-14 12:37 ` Koning, Paul [this message]
2022-10-14 14:38 ` Jeff Law
2022-10-14 16:37 ` Koning, Paul
2022-10-14 17:10 ` Jeff Law
2022-10-14 17:36 ` Koning, Paul
2022-10-14 21:15 ` Jeff Law
2022-10-14 21:21 ` Koning, Paul
2022-10-14 21:30 ` Jeff Law
2022-10-15 0:19 ` Jeff Law
2022-10-14 16:39 ` Richard Biener
2022-10-14 17:11 ` Jeff Law
2022-10-14 4:47 ` Jeff Law
2022-10-14 16:37 ` Segher Boessenkool
2022-10-14 17:07 ` Jeff Law
2022-10-14 17:35 ` Segher Boessenkool
2022-10-14 18:03 ` Jeff Law
2022-10-14 19:58 ` Koning, Paul
2022-10-14 20:12 ` Segher Boessenkool
2022-10-14 20:40 ` Koning, Paul
2022-10-14 6:20 ` Takayuki 'January June' Suwa
2022-10-14 16:25 ` Segher Boessenkool
2022-10-15 3:18 ` Takayuki 'January June' Suwa
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=7C52148F-A6D1-475F-B19D-2C340770B8EC@dell.com \
--to=paul.koning@dell.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.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).