public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Greg McGary <gkm@rivosinc.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
	Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] combine: Don't optimize SIGN_EXTEND of MEM on WORD_REGISTER_OPERATIONS targets [PR113010]
Date: Thu, 1 Feb 2024 18:24:27 -0700	[thread overview]
Message-ID: <03b351a0-a5f4-48ab-bc67-765eabf5dbcd@rivosinc.com> (raw)
In-Reply-To: <cb97e417-a04c-4913-876d-2276f7e3015c@gmail.com>

On 1/18/24 9:24 AM, Jeff Law wrote:
>
> On 1/17/24 20:53, Greg McGary wrote:
>>
>> While the code comment is true, perhaps it obscures the primary intent,
>> which is recognition that the pattern (SIGN_EXTEND (mem ...) ) is 
>> destined
>> to expand into a single memory-load instruction and no simplification is
>> possible, so why waste time with further analysis or transformation? 
>> There
>> are plenty of other conditions that also short circuit to "do 
>> nothing" and
>> this seems just as straightforward as those others. Efforts to catch 
>> this
>> further downstream add gratuitous complexity.
> Because the real bug is likely still lurking, waiting for something 
> else to trigger it.
>
> An early exit is fine when we're just trying to avoid unnecessary 
> work, but there's something else going on here we need to understand 
> first.


expand_compound_operation() wants to evaluate the sign- and 
zero-extension of MEM. It begins by calling gen_lowpart(), which returns 
the same result in both cases: a paradoxical subreg of a MEM (PSoM). 
What is the value of the high part of a PSoM? Can that high part be 
evaluated at compile time?

According to existing code, the high part of a PSoM is statically 0. 
However, for a machine where (WORD_REGISTER_OPERATIONS && load_extend_op 
(inner_mode) == SIGN_EXTEND), the high part of a PSoM is  only known at 
runtime as 0s or 1s. That's the downstream bug. The fix for such 
machines is either (A) forbid static evaluation of the high part of a 
PSoM, or (B) forbid transforming (SIGN_EXTEND (MEM ...) ) into a PSoM. 
My patch does B. Perhaps you prefer A? The trouble with A is that in the 
zero-extend case, it is valid to statically evaluate as 0. It is only 
the sign-extend case that isn't known until runtime. By the time we have 
a PSoM, its upstream ancestor as sign- or zero-extend is already lost.

Does that give you the understanding you desire, or are there deeper 
mysteries to probe?

G


  reply	other threads:[~2024-02-02  1:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 22:19 Greg McGary
2024-01-17  6:44 ` Richard Biener
2024-01-18  3:53   ` Greg McGary
2024-01-18 16:24     ` Jeff Law
2024-02-02  1:24       ` Greg McGary [this message]
2024-02-02  5:24         ` Jeff Law
2024-02-02 22:48           ` Greg McGary
2024-02-05  4:58             ` Jeff Law
2024-02-08  5:36               ` Greg McGary
2024-01-17  7:56 ` YunQiang Su

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=03b351a0-a5f4-48ab-bc67-765eabf5dbcd@rivosinc.com \
    --to=gkm@rivosinc.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=richard.guenther@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).