From: Richard Sandiford <richard.sandiford@arm.com>
To: Alex Coplan <alex.coplan@arm.com>
Cc: gcc-patches@gcc.gnu.org,
Richard Earnshaw <richard.earnshaw@arm.com>,
Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Subject: Re: [PATCH v2 06/11] aarch64: Fix up aarch64_print_operand xzr/wzr case
Date: Tue, 05 Dec 2023 16:13:01 +0000 [thread overview]
Message-ID: <mptedg039wy.fsf@arm.com> (raw)
In-Reply-To: <ZW8BTQWe6/1wk+Qo@arm.com> (Alex Coplan's message of "Tue, 5 Dec 2023 10:54:05 +0000")
Alex Coplan <alex.coplan@arm.com> writes:
> Hi,
>
> This is a v2 of:
>
> https://gcc.gnu.org/pipermail/gcc-patches/2023-November/637612.html
>
> v1 was approved as-is, but this version pulls out the test into a helper
> function which is used by later patches in the series.
>
> Bootstrapped/regtested as a series on aarch64-linux-gnu, OK for trunk?
>
> Thanks,
> Alex
>
> -- >8 --
>
> This adjusts aarch64_print_operand to recognize zero rtxes in modes other than
> VOIDmode. This allows us to use xzr/wzr for zero vectors, for example.
>
> We extract the test into a helper function, aarch64_const_zero_rtx_p, since this
> predicate is needed by later patches.
>
> gcc/ChangeLog:
>
> * config/aarch64/aarch64-protos.h (aarch64_const_zero_rtx_p): New.
> * config/aarch64/aarch64.cc (aarch64_const_zero_rtx_p): New.
> Use it ...
> (aarch64_print_operand): ... here. Recognize CONST0_RTXes in
> modes other than VOIDmode.
>
> diff --git a/gcc/config/aarch64/aarch64-protos.h b/gcc/config/aarch64/aarch64-protos.h
> index d2718cc87b3..27fc6ccf098 100644
> --- a/gcc/config/aarch64/aarch64-protos.h
> +++ b/gcc/config/aarch64/aarch64-protos.h
> @@ -773,6 +773,7 @@ bool aarch64_expand_cpymem (rtx *);
> bool aarch64_expand_setmem (rtx *);
> bool aarch64_float_const_zero_rtx_p (rtx);
> bool aarch64_float_const_rtx_p (rtx);
> +bool aarch64_const_zero_rtx_p (rtx);
> bool aarch64_function_arg_regno_p (unsigned);
> bool aarch64_fusion_enabled_p (enum aarch64_fusion_pairs);
> bool aarch64_gen_cpymemqi (rtx *);
> diff --git a/gcc/config/aarch64/aarch64.cc b/gcc/config/aarch64/aarch64.cc
> index fca64daf2a0..a35c6bbe335 100644
> --- a/gcc/config/aarch64/aarch64.cc
> +++ b/gcc/config/aarch64/aarch64.cc
> @@ -9095,6 +9095,15 @@ aarch64_float_const_zero_rtx_p (rtx x)
> return real_equal (CONST_DOUBLE_REAL_VALUE (x), &dconst0);
> }
>
> +/* Return true if X is any kind of constant zero rtx. */
> +
> +bool
> +aarch64_const_zero_rtx_p (rtx x)
> +{
> + return x == CONST0_RTX (GET_MODE (x))
> + || (CONST_DOUBLE_P (x) && aarch64_float_const_zero_rtx_p (x));
> +}
> +
Think this is easier to read if formatted as:
return (x == CONST0_RTX (GET_MODE (x))
|| (CONST_DOUBLE_P (x) && aarch64_float_const_zero_rtx_p (x)));
OK with that change (or as-is if you prefer). Thanks for splitting
the function out.
Richard
> /* Return TRUE if rtx X is immediate constant that fits in a single
> MOVI immediate operation. */
> bool
> @@ -9977,8 +9986,7 @@ aarch64_print_operand (FILE *f, rtx x, int code)
>
> case 'w':
> case 'x':
> - if (x == const0_rtx
> - || (CONST_DOUBLE_P (x) && aarch64_float_const_zero_rtx_p (x)))
> + if (aarch64_const_zero_rtx_p (x))
> {
> asm_fprintf (f, "%czr", code);
> break;
prev parent reply other threads:[~2023-12-05 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 10:54 Alex Coplan
2023-12-05 16:13 ` Richard Sandiford [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=mptedg039wy.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=alex.coplan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.com \
--cc=richard.earnshaw@arm.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).