public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>
To: Richard Sandiford <Richard.Sandiford@arm.com>,
	Andrea Corallo <Andrea.Corallo@arm.com>
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>, nd <nd@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: RE: [PATCH] aarch64: Do not alter value on a force_reg returned rtx expanding __jcvt
Date: Mon, 21 Sep 2020 11:00:32 +0000	[thread overview]
Message-ID: <DB7PR08MB30021D3CAFA9D1A5F2B2D7AC933A0@DB7PR08MB3002.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <mptpn6fpfaj.fsf@arm.com>

Hi Andrea,

> -----Original Message-----
> From: Gcc-patches <gcc-patches-bounces@gcc.gnu.org> On Behalf Of
> Richard Sandiford
> Sent: 21 September 2020 11:58
> To: Andrea Corallo <Andrea.Corallo@arm.com>
> Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>; nd <nd@arm.com>;
> gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] aarch64: Do not alter value on a force_reg returned rtx
> expanding __jcvt
> 
> Andrea Corallo <andrea.corallo@arm.com> writes:
> > Hi all,
> >
> > From the `force_reg` description comment I see the returned register
> > should not be modified, thus IIUC should not be used as a GEN_FCN
> > target.
> >
> > Assuming my interpretation is correct this fix this case inside
> > `aarch64_general_expand_builtin` while expanding expanding the
> > `__jcvt` intrinsic.  If is not the case please discard.
> 
> Good catch.

Can you please also backport it to the appropriate branches as well after some time on trunk.
Thanks,
Kyrill

> 
> > Regtested and bootsraped on aarch64-linux-gnu.
> >
> >   Andrea
> >
> > From 403ad66b8f9c108d7f38b406ed1afcb603b7e25f Mon Sep 17 00:00:00
> 2001
> > From: Andrea Corallo <andrea.corallo@arm.com>
> > Date: Thu, 17 Sep 2020 17:17:52 +0100
> > Subject: [PATCH] aarch64: Do not alter value on a force_reg returned rtx
> >  expanding __jcvt
> >
> > 2020-09-17  Andrea Corallo  <andrea.corallo@arm.com>
> >
> > 	* config/aarch64/aarch64-builtins.c
> > 	(aarch64_general_expand_builtin): Use expand machinery not to
> > 	alter the value of an rtx returned by force_reg.
> 
> OK, thanks.
> 
> Richard
> 
> > ---
> >  gcc/config/aarch64/aarch64-builtins.c | 16 ++++++++--------
> >  1 file changed, 8 insertions(+), 8 deletions(-)
> >
> > diff --git a/gcc/config/aarch64/aarch64-builtins.c
> b/gcc/config/aarch64/aarch64-builtins.c
> > index 4f33dd936c7..b787719cf5e 100644
> > --- a/gcc/config/aarch64/aarch64-builtins.c
> > +++ b/gcc/config/aarch64/aarch64-builtins.c
> > @@ -2128,14 +2128,14 @@ aarch64_general_expand_builtin (unsigned int
> fcode, tree exp, rtx target,
> >        return target;
> >
> >      case AARCH64_JSCVT:
> > -      arg0 = CALL_EXPR_ARG (exp, 0);
> > -      op0 = force_reg (DFmode, expand_normal (arg0));
> > -      if (!target)
> > -	target = gen_reg_rtx (SImode);
> > -      else
> > -	target = force_reg (SImode, target);
> > -      emit_insn (GEN_FCN (CODE_FOR_aarch64_fjcvtzs) (target, op0));
> > -      return target;
> > +      {
> > +	expand_operand ops[2];
> > +	create_output_operand (&ops[0], target, SImode);
> > +	op0 = expand_normal (CALL_EXPR_ARG (exp, 0));
> > +	create_input_operand (&ops[1], op0, DFmode);
> > +	expand_insn (CODE_FOR_aarch64_fjcvtzs, 2, ops);
> > +	return ops[0].value;
> > +      }
> >
> >      case AARCH64_SIMD_BUILTIN_FCMLA_LANEQ0_V2SF:
> >      case AARCH64_SIMD_BUILTIN_FCMLA_LANEQ90_V2SF:

  reply	other threads:[~2020-09-21 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 10:31 Andrea Corallo
2020-09-21 10:58 ` Richard Sandiford
2020-09-21 11:00   ` Kyrylo Tkachov [this message]
2020-09-21 12:13     ` Andrea Corallo
2020-09-24  9:50       ` Andrea Corallo

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=DB7PR08MB30021D3CAFA9D1A5F2B2D7AC933A0@DB7PR08MB3002.eurprd08.prod.outlook.com \
    --to=kyrylo.tkachov@arm.com \
    --cc=Andrea.Corallo@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=Richard.Sandiford@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nd@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).