From: Segher Boessenkool <firstname.lastname@example.org>
To: Roger Sayle <email@example.com>
Subject: Re: [PATCH] Add new target hook: simplify_modecc_const.
Date: Tue, 26 Jul 2022 17:11:16 -0500 [thread overview]
Message-ID: <20220726221116.GC25951@gate.crashing.org> (raw)
On Tue, Jul 26, 2022 at 10:04:45PM +0100, Roger Sayle wrote:
> It's very important to distinguish the invariants that exist for the RTL
> data structures as held in memory (rtx),
"In memory"? What does that mean here? RTX are just RTL expressions,
nothing more, nothing less.
> vs. the use of "enum rtx_code"s,
> "machine_mode"s and operands in the various processing functions
> of the middle-end.
> Yes, it's very true that RTL integer constants don't specify a mode
> (are VOIDmode), so therefore operations like ZERO_EXTEND or EQ
> don't make sense with all constant operands.
ZERO_EXTEND makes sense for all non-negative operands and no negative
operands. Anything with some integer mode (so not VOIDmode!) can be
the first argument to EQ, at least structurally.
> This is (one reason)
> why constant-only operands are disallowed from RTL (data structures),
> and why in APIs that perform/simplify these operations, the original
> operand mode (of the const_int(s)) must be/is always passed as a
> Hence, for say simplify_const_binary_operation, op0 and op1 can
> both be const_int, as the mode argument specifies the mode of the
> "code" operation. Likewise, in simplify_relational_operation, both
> op0 and op1 may be CONST_INT as "cmp_mode" explicitly specifies
> the mode that the operation is performed in and "mode" specifies
> the mode of the result.
> Your comment that "comparing two integer constants is invalid
> RTL *in all contexts*" is a serious misunderstanding of what's
> going on.
Not at all. I showed the quote from the documentation: it is always
invalid to have two VOIDmode arguments to COMPARE.
> At no point is a RTL rtx node ever allocated with two
> integer constant operands. RTL simplification is for hypothetical
> "what if" transformations (just like try_combine calls recog with
> RTL that may not be real instructions), and these simplifcations
> are even sometimes required to preserve the documented RTL
> invariants. Comparisons of two integers must be simplified to
> true/false precisely to ensure that they never appear in an actual
> COMPARE node.
As the function documentation clearly states, two VOIDmode args (and
MODE that as well) is a special case for infinite precision arithmetic.
> I worry this fundamental misunderstanding is the same issue that
> has been holding up understanding/approving a previous patch:
Let's not discuss this in this thread though.
> For a related bug, consider PR rtl-optimization/67382, that's assigned
> to you in bugzilla. In this case, the RTL optimizers know that both
> operands to a COMPARE are integer constants (both -2), yet the
> compiler still performs a run-time comparison and conditional jump:
> movl $-2, %eax
> movl %eax, 12(%rsp)
> cmpl $-2, %eax
> je .L1
> Failing to optimize/consider a comparison between two integer
> constants *in any context* just leads to poor code.
If combine would ever generate invalid RTL, the resulting insn does not
pass recog(), making the combine attempt fail. This is not the way.
The simplifier (part of combine) has a function to actually simplify
tautologies and contradictions, the simplify_const_relational_operation
function you edited here.
> Hopefully, this clears up that the documented constraints on RTL rtx
> aren't exactly the same as the constraints on the use of rtx_codes in
> simplify-rtx's functional APIs. So simplify_subreg really gets called
> on operands that are neither REG nor MEM, as this is unrelated to
> what the documentation of the SUBREG rtx specifies.
Thank you for telling the maintainer of combine the basics of what all
of this does! I hadn't noticed any of that before.
> If you don't believe that op0 and op1 can ever both be const_int
> in this function, perhaps consider it harmless dead code and humor
They can be, as clearly documented (and obvious from the code), but you
can not ever have that in the RTL stream, which is needed for your patch
to do anything.
I consider it harmful, and not dead. Sorry.
Do you have comments on the rest?
next prev parent reply other threads:[~2022-07-26 22:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 21:08 [PATCH] Be careful with MODE_CC in simplify_const_relational_operation Roger Sayle
2022-07-07 22:38 ` Segher Boessenkool
2022-07-26 12:13 ` [PATCH] Add new target hook: simplify_modecc_const Roger Sayle
2022-07-26 17:44 ` Segher Boessenkool
2022-07-26 21:04 ` Roger Sayle
2022-07-26 22:11 ` Segher Boessenkool [this message]
2022-07-27 7:51 ` Roger Sayle
2022-07-27 18:37 ` Segher Boessenkool
2022-07-28 12:39 ` Richard Sandiford
2022-10-10 15:50 ` H.J. Lu
2022-10-14 20:31 ` Jeff Law
2022-10-14 21:05 ` H.J. Lu
2022-10-14 20:26 ` Jeff Law
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).