Re: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-12-06 Thread Richard Sandiford via Gcc-patches
Tamar Christina writes: >> -Original Message- >> From: Richard Sandiford >> Sent: Tuesday, December 6, 2022 10:28 AM >> To: Tamar Christina >> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw >> ; Marcus Shawcroft >> ; Kyrylo Tkachov >&g

RE: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-12-06 Thread Tamar Christina via Gcc-patches
> -Original Message- > From: Richard Sandiford > Sent: Tuesday, December 6, 2022 10:28 AM > To: Tamar Christina > Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw > ; Marcus Shawcroft > ; Kyrylo Tkachov > Subject: Re: [PATCH 5/8]AArch64 aarch64: Make

Re: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-12-06 Thread Richard Sandiford via Gcc-patches
Tamar Christina writes: > Hi, > > >> This name might cause confusion with the SVE iterators, where FULL means >> "every bit of the register is used". How about something like VMOVE >> instead? >> >> With this change, I guess VALL_F16 represents "The set of all modes for >> which the vld1 intrins

RE: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-11-29 Thread Tamar Christina via Gcc-patches
gt; To: Richard Sandiford > > Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw > > ; Marcus Shawcroft > > ; Kyrylo Tkachov > > > Subject: RE: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable. > > > > Hi, > > > > > > > This name

RE: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-11-22 Thread Tamar Christina via Gcc-patches
> ; Marcus Shawcroft > ; Kyrylo Tkachov > Subject: RE: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable. > > Hi, > > > > This name might cause confusion with the SVE iterators, where FULL > > means "every bit of the register is used". How about som

RE: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-11-11 Thread Tamar Christina via Gcc-patches
Hi, > This name might cause confusion with the SVE iterators, where FULL means > "every bit of the register is used". How about something like VMOVE > instead? > > With this change, I guess VALL_F16 represents "The set of all modes for > which the vld1 intrinsics are provided" and VMOVE or what

RE: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-11-01 Thread Tamar Christina via Gcc-patches
> -Original Message- > From: Richard Sandiford > Sent: Tuesday, November 1, 2022 2:59 PM > To: Tamar Christina > Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw > ; Marcus Shawcroft > ; Kyrylo Tkachov > Subject: Re: [PATCH 5/8]AArch64 aarch64: Make existing V2

Re: [PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-11-01 Thread Richard Sandiford via Gcc-patches
Tamar Christina writes: > Hi All, > > The backend has an existing V2HFmode that is used by pairwise operations. > This mode was however never made fully functional. Amongst other things it > was > never declared as a vector type which made it unusable from the mid-end. > > It's also lacking an i

[PATCH 5/8]AArch64 aarch64: Make existing V2HF be usable.

2022-10-31 Thread Tamar Christina via Gcc-patches
Hi All, The backend has an existing V2HFmode that is used by pairwise operations. This mode was however never made fully functional. Amongst other things it was never declared as a vector type which made it unusable from the mid-end. It's also lacking an implementation for load/stores so reload