Yes, RISC-V riscv.h defined the WORD_REGISTER_OPERATIONS to be 1, while
aarch64.h defined it as 0, with below comments. No idea this can fit RISC-V or
not.
/* WORD_REGISTER_OPERATIONS does not hold for AArch64.
The assigned word_mode is DImode but operations narrower than SImode
behave as 32-bit operations if using the W-form of the registers rather
than as word_mode (64-bit) operations as WORD_REGISTER_OPERATIONS
expects. */
#define WORD_REGISTER_OPERATIONS 0
Pan
-----Original Message-----
From: Gcc-patches <gcc-patches-bounces+pan2.li=intel....@gcc.gnu.org> On Behalf
Of Richard Sandiford via Gcc-patches
Sent: Thursday, April 6, 2023 5:31 PM
To: Jeff Law <jeffreya...@gmail.com>
Cc: Jakub Jelinek <ja...@redhat.com>; Richard Biener <rguent...@suse.de>; Eric
Botcazou <botca...@adacore.com>; gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] dse: Handle SUBREGs of word REGs differently for
WORD_REGISTER_OPERATIONS targets [PR109040]
Jeff Law <jeffreya...@gmail.com> writes:
> On 4/5/23 10:48, Jakub Jelinek wrote:
>> On Wed, Apr 05, 2023 at 10:17:59AM -0600, Jeff Law wrote:
>>>> It is true that an instruction like (insn 8 7 9 2 (set (reg:HI 141)
>>>> (subreg:HI (reg:SI 142) 0)) "aauu.c":6:18 181 {*movhi_internal}
>>>> (nil))
>>>> can appear in the IL on WORD_REGISTER_OPERATIONS target, but I
>>>> think the upper bits shouldn't be random garbage in that case, it
>>>> should be zero extended or sign extended.
>>> Well, that's one of the core questions here. What are the state of
>>> the upper 16 bits of (reg:HI 141)? The WORD_REGISTER_OPERATIONS
>>> docs aren't 100% clear as we're not really doing any operation.
>>>
>>> So again, I think we need to decide if the DSE transformation is
>>> correct or not. I *think* we can aggree that insn 39 is OK. It's
>>> really the semantics of insn 47 that I think we need to agree on.
>>> What is the state of the upper
>>> 16 bits of (reg:HI 175) after insn 47?
>>
>> I'm afraid I don't know the answers here, I think Eric is
>> WORD_REGISTER_OPERATIONS expert here I think these days (most of the
>> major targets are !WORD_REGISTER_OPERATIONS).
> Hopefully he'll chime in.
Just curious: have you experimented with making RISC-V
!WORD_REGISTER_OPERATIONS too? Realise it's not the right way to fix the bug,
just curious in general.
Not defining it seems to have worked well for AArch64. And IMO the semantics
are much easier to follow when there is no special treatment of upper bits.
Subregs are hard enough to reason about as it is...
Richard
