Re: [PATCH] vinsertps XMM16-XMM31 fixes

2016-05-12 Thread Kirill Yukhin
On 09 May 18:47, Jakub Jelinek wrote: > Hi! > > The testcases show that we emit AVX512BW instructions even when > AVX512BW is disabled. Additionally, two of the 4 patterns were using > weirdo constraint for the output (x instead of v, while they used v for > input). > > Fixed thusly, bootstrappe

Re: [PATCH] vinsertps XMM16-XMM31 fixes

2016-05-12 Thread Kirill Yukhin
Hi, On 09 May 18:45, Jakub Jelinek wrote: > Hi! > > vinsertps is already in AVX512F, so we can use use v constraints > freely. > > Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? OK. -- Thanks, K > > 2016-05-09 Jakub Jelinek > > * config/i386/sse.md (*vec_setv4sf_

[PATCH] vinsertps XMM16-XMM31 fixes

2016-05-09 Thread Jakub Jelinek
Hi! The testcases show that we emit AVX512BW instructions even when AVX512BW is disabled. Additionally, two of the 4 patterns were using weirdo constraint for the output (x instead of v, while they used v for input). Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok for tru

[PATCH] vinsertps XMM16-XMM31 fixes

2016-05-09 Thread Jakub Jelinek
Hi! vinsertps is already in AVX512F, so we can use use v constraints freely. Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk? 2016-05-09 Jakub Jelinek * config/i386/sse.md (*vec_setv4sf_sse4_1, sse4_1_insertps): Use v constraint instead of x in avx alterna