PING^7: [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2020-02-13 Thread H.J. Lu
On Thu, Feb 6, 2020 at 8:17 PM H.J. Lu wrote: > > On Mon, Jan 27, 2020 at 10:59 AM H.J. Lu wrote: > > > > On Mon, Jul 8, 2019 at 8:19 AM H.J. Lu wrote: > > > > > > On Tue, Jun 18, 2019 at 8:59 AM H.J. Lu wrote: > > > > > > > > On Fri, May 31, 2019 at 10:38 AM H.J. Lu wrote: > > > > > > > > > >

PING^6: [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2020-02-06 Thread H.J. Lu
ewise. > > > > > > (*movtf_internal): Call ix86_output_ssemov for TYPE_SSEMOV. > > > > > > (*movdf_internal): Call ix86_output_ssemov for TYPE_SSEMOV. > > > > > > Remove TARGET_AVX512F, TARGET_PREFER_AVX256, TARGET_AVX512VL > > > > >

PING^5: [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2020-01-27 Thread H.J. Lu
_AVX512F, TARGET_PREFER_AVX256, TARGET_AVX512VL > > > > > and ext_sse_reg_operand check. > > > > > (*movsf_internal_avx): Call ix86_output_ssemov for > > > > > TYPE_SSEMOV. > > > > > Remove TARGET_PREFER_AVX256, TARGE

Re: [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2019-07-22 Thread Jeff Law
On 2/22/19 9:24 AM, H.J. Lu wrote: > Hi Jan, Uros, > > This patch fixes the wrong code bug: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 > > Tested on AVX2 and AVX512 with and without --with-arch=native. > > OK for trunk? > > Thanks. > > H.J. > -- > i386 backend has > > INT_MODE (O

PING^4: [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2019-07-08 Thread H.J. Lu
On Tue, Jun 18, 2019 at 8:59 AM H.J. Lu wrote: > > On Fri, May 31, 2019 at 10:38 AM H.J. Lu wrote: > > > > On Tue, May 21, 2019 at 2:43 PM H.J. Lu wrote: > > > > > > On Fri, Feb 22, 2019 at 8:25 AM H.J. Lu wrote: > > > > > > > > Hi Jan, Uros, > > > > > > > > This patch fixes the wrong code bug:

PING^3: [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2019-06-18 Thread H.J. Lu
On Fri, May 31, 2019 at 10:38 AM H.J. Lu wrote: > > On Tue, May 21, 2019 at 2:43 PM H.J. Lu wrote: > > > > On Fri, Feb 22, 2019 at 8:25 AM H.J. Lu wrote: > > > > > > Hi Jan, Uros, > > > > > > This patch fixes the wrong code bug: > > > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 > >

PING^2: [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2019-05-31 Thread H.J. Lu
On Tue, May 21, 2019 at 2:43 PM H.J. Lu wrote: > > On Fri, Feb 22, 2019 at 8:25 AM H.J. Lu wrote: > > > > Hi Jan, Uros, > > > > This patch fixes the wrong code bug: > > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 > > > > Tested on AVX2 and AVX512 with and without --with-arch=native. >

PING^1: [PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2019-05-21 Thread H.J. Lu
On Fri, Feb 22, 2019 at 8:25 AM H.J. Lu wrote: > > Hi Jan, Uros, > > This patch fixes the wrong code bug: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 > > Tested on AVX2 and AVX512 with and without --with-arch=native. > > OK for trunk? > > Thanks. > > H.J. > -- > i386 backend has > > INT

[PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2019-02-22 Thread H.J. Lu
Hi Jan, Uros, This patch fixes the wrong code bug: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 Tested on AVX2 and AVX512 with and without --with-arch=native. OK for trunk? Thanks. H.J. -- i386 backend has INT_MODE (OI, 32); INT_MODE (XI, 64); So, XI_MODE represents 64 INTEGER bytes =

[PATCH] i386: Properly encode xmm16-xmm31/ymm16-ymm31 for vector move

2019-02-13 Thread H.J. Lu
On Mon, Feb 11, 2019 at 05:24:24PM +0100, Jakub Jelinek wrote: > On Mon, Feb 11, 2019 at 04:56:45PM +0100, Uros Bizjak wrote: > > > Let's first define what MODE_XI means in standard_sse_constant_opcode > > > as well as in all these mov patterns for with and without AVX512VL. > > > Without > > >