[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-13 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 H.J. Lu changed: What|Removed |Added Attachment #45705|0 |1 is obsolete|

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-13 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 H.J. Lu changed: What|Removed |Added Attachment #45685|0 |1 is obsolete|

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-13 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #19 from H.J. Lu --- sse.md has (define_insn "mov_internal" [(set (match_operand:VMOVE 0 "nonimmediate_operand" "=v,v ,v ,m") (match_operand:VMOVE 1 "nonimmediate_or_sse_const_operand" " C,BC,vm,v"))]

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #18 from H.J. Lu --- (In reply to Jakub Jelinek from comment #14) > Comment on attachment 45685 [details] > I am testing this > > The movsi change doesn't look entirely right to me. While OImode or TImode > is not allowed in ext

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #17 from H.J. Lu --- [hjl@gnu-4 gcc]$ cat /tmp/z.c /* { dg-do compile { target { ! ia32 } } } */ /* { dg-options "-O2 -march=skylake-avx512" } */ extern long long i; long long foo1 (void) { register long long xmm16 __asm

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #16 from H.J. Lu --- [hjl@gnu-4 gcc]$ cat /tmp/y.c /* { dg-do compile { target { ! ia32 } } } */ /* { dg-options "-O2 -march=skylake-avx512 -mprefer-vector-width=512" } */ extern float d; void foo1 (float x) { register float

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #15 from H.J. Lu --- [hjl@gnu-4 gcc]$ cat /tmp/x.c /* { dg-do compile { target { ! ia32 } } } */ /* { dg-options "-O2 -march=skylake-avx512 -mprefer-vector-width=512" } */ extern double d; void foo1 (double x) { register double

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #14 from Jakub Jelinek --- Comment on attachment 45685 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45685 I am testing this The movsi change doesn't look entirely right to me. While OImode or TImode is not allowed in ext

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 H.J. Lu changed: What|Removed |Added Target Milestone|7.5 |9.0

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #13 from H.J. Lu --- Created attachment 45685 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45685=edit I am testing this

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #12 from H.J. Lu --- [hjl@gnu-4 tmp]$ cat x.c /* { dg-do compile } */ /* { dg-options "-O2 -march=skylake-avx512" } */ extern int i; int foo1 (void) { register int xmm16 __asm ("xmm16") = i; asm volatile ("" : "+v" (xmm16));

[Bug target/89229] Unnecessary ZMM in movoi_internal_avx/movti_internal

2019-02-12 Thread hjl.tools at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89229 --- Comment #11 from H.J. Lu --- (In reply to Jakub Jelinek from comment #10) > Though, is this really a regression? I mean, have we ever emitted better > code? It isn't a regression.