This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [PATCH 5/5][AArch64] fp16fml support


Patch updated per Richard's comments. Ok for trunk?

-----Original Message-----
From: Richard Sandiford [mailto:richard.sandiford@linaro.org] 
Sent: Thursday, January 4, 2018 8:02 AM
To: Michael Collison <Michael.Collison@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>; nd <nd@arm.com>
Subject: Re: [PATCH 5/5][AArch64] fp16fml support

Hi Michael,

Not a review of the full patch, just a comment about the patterns:

Michael Collison <Michael.Collison@arm.com> writes:
> +(define_expand "aarch64_fml<f16mac1>l_lane_lowv2sf"
> +  [(set (match_operand:V2SF 0 "register_operand" "")
> +	(unspec:V2SF [(match_operand:V2SF 1 "register_operand" "")
> +			   (match_operand:V4HF 2 "register_operand" "")
> +			   (match_operand:V4HF 3 "register_operand" "")
> +			   (match_operand:SI 4 "aarch64_imm2" "")]
> +	 VFMLA16_LOW))]
> +  "TARGET_F16FML"
> +{
> +    rtx p1 = aarch64_simd_vect_par_cnst_half (V4HFmode,
> +					      GET_MODE_NUNITS (V4HFmode),
> +					      false);
> +    rtx lane = GEN_INT (ENDIAN_LANE_N (GET_MODE_NUNITS (SImode), INTVAL (operands[4])));

Please use the newly-introduced aarch64_endian_lane_rtx for this.

GET_MODE_NUNITS (SImode) doesn't seem right though, since that's always 1.
Should it be using V4HFmode instead?

Same for the other patterns.

Thanks,
Richard

Attachment: fp16fml_up_v2.patch
Description: fp16fml_up_v2.patch


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]