Re: [Patch] [arm] Ensure *neon_mov constraint uses correct mode.

2019-04-08 Thread Kyrill Tkachov
On 4/8/19 4:51 PM, Matthew Malcomson wrote: On 08/04/19 14:00, Kyrill Tkachov wrote: Hi Matthew, On 4/5/19 12:06 PM, Matthew Malcomson wrote: Bootstrapped and regtested on arm-none-linux-gnueabihf Regtested on cross-compiler arm-none-eabi Does this fix a PR? If so, could you add the infor

Re: [Patch] [arm] Ensure *neon_mov constraint uses correct mode.

2019-04-08 Thread Matthew Malcomson
On 08/04/19 14:00, Kyrill Tkachov wrote: > Hi Matthew, > > On 4/5/19 12:06 PM, Matthew Malcomson wrote: >> >> Bootstrapped and regtested on arm-none-linux-gnueabihf >> Regtested on cross-compiler arm-none-eabi >> > > Does this fix a PR? > > If so, could you add the information for it to the Cha

Re: [Patch] [arm] Ensure *neon_mov constraint uses correct mode.

2019-04-08 Thread Kyrill Tkachov
Hi Matthew, On 4/5/19 12:06 PM, Matthew Malcomson wrote: Hi there, The "*neon_mov" patterns for 128 bit sized quantities uses the "Dn" constraint to match vmov.f32 and vmov.i patterns. This constraint boils down to using the `neon_immediate_valid` function. Once the constraint has matched, the

[Patch] [arm] Ensure *neon_mov constraint uses correct mode.

2019-04-05 Thread Matthew Malcomson
Hi there, The "*neon_mov" patterns for 128 bit sized quantities uses the "Dn" constraint to match vmov.f32 and vmov.i patterns. This constraint boils down to using the `neon_immediate_valid` function. Once the constraint has matched, the output C statement asserts that function passes. The output