Re: [PATCH V2] [x86] Fix incorrect digit constraint

2022-11-01 Thread Hongtao Liu via Gcc-patches
On Mon, Oct 31, 2022 at 5:22 PM Uros Bizjak wrote: > > On Mon, Oct 31, 2022 at 2:10 AM liuhongt wrote: > > > > >You have a couple of other patterns where operand 1 is matched to > > >produce vmovddup insn. These are *avx512f_unpcklpd512 and > > >avx_unpcklpd256. You can also remove expander in bo

Re: [PATCH V2] [x86] Fix incorrect digit constraint

2022-10-31 Thread Uros Bizjak via Gcc-patches
On Mon, Oct 31, 2022 at 2:10 AM liuhongt wrote: > > >You have a couple of other patterns where operand 1 is matched to > >produce vmovddup insn. These are *avx512f_unpcklpd512 and > >avx_unpcklpd256. You can also remove expander in both > >cases. > > Yes, changed in V2 patch. > > Bootstrapped and

[PATCH V2] [x86] Fix incorrect digit constraint

2022-10-30 Thread liuhongt via Gcc-patches
>You have a couple of other patterns where operand 1 is matched to >produce vmovddup insn. These are *avx512f_unpcklpd512 and >avx_unpcklpd256. You can also remove expander in both >cases. Yes, changed in V2 patch. Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}. Ok for trunk? Matching