From: Alex Coplan <alex.coplan@arm.com>
To: Andrew Pinski <quic_apinski@quicinc.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] aarch64: Fix undefinedness while testing the J constraint [PR100204]
Date: Fri, 26 Jan 2024 10:07:38 +0000 [thread overview]
Message-ID: <ZbOEagZ4oN/H7idd@arm.com> (raw)
In-Reply-To: <20240125195712.410550-1-quic_apinski@quicinc.com>
On 25/01/2024 11:57, Andrew Pinski wrote:
> The J constraint can invoke undefined behavior due to it taking the
> negative of the ival if ival was HWI_MIN. The fix is simple as casting
> to `unsigned HOST_WIDE_INT` before doing the negative of it. This
> does that.
Thanks for doing this.
>
> Committed as obvious after build/test for aarch64-linux-gnu.
>
> gcc/ChangeLog:
>
> PR target/100204
> * config/aarch64/constraints.md (J): Cast to `unsigned HOST_WIDE_INT`
> before taking the negative of it.
>
> Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>
> ---
> gcc/config/aarch64/constraints.md | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/config/aarch64/constraints.md b/gcc/config/aarch64/constraints.md
> index 8566befd727..a2569cea510 100644
> --- a/gcc/config/aarch64/constraints.md
> +++ b/gcc/config/aarch64/constraints.md
> @@ -118,7 +118,7 @@ (define_constraint "Uat"
> (define_constraint "J"
> "A constant that can be used with a SUB operation (once negated)."
> (and (match_code "const_int")
> - (match_test "aarch64_uimm12_shift (-ival)")))
> + (match_test "aarch64_uimm12_shift (- (unsigned HOST_WIDE_INT) ival)")))
Sorry for the nitpick, but: I don't think we want a space after the unary -
here (at least according to https://gcc.gnu.org/codingconventions.html).
Alex
>
> ;; We can't use the mode of a CONST_INT to determine the context in
> ;; which it is being used, so we must have a separate constraint for
> --
> 2.39.3
>
prev parent reply other threads:[~2024-01-26 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 19:57 Andrew Pinski
2024-01-26 10:07 ` Alex Coplan [this message]
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=ZbOEagZ4oN/H7idd@arm.com \
--to=alex.coplan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=quic_apinski@quicinc.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).