[Bug target/89040] [9 Regressiom] Wrong code with -mno-mmx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89040 Richard Biener changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Known to fail||9.5.0 Target Milestone|9.5 |10.0 --- Comment #6 from Richard Biener --- Fixed for GCC 10.
[Bug target/89040] [9 Regressiom] Wrong code with -mno-mmx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89040 Mikael Pettersson changed: What|Removed |Added CC||mikpelinux at gmail dot com --- Comment #5 from Mikael Pettersson --- According to my git bisect, this was fixed for gcc-10.1.0 by d4410ec0ab4e3d2c834a811acf9e39af32e1d1d8 is the first new commit commit d4410ec0ab4e3d2c834a811acf9e39af32e1d1d8 Author: H.J. Lu Date: Wed May 15 15:31:18 2019 + i386: Allow MMX vector expanders with TARGET_MMX_WITH_SSE PR target/89021 ... From-SVN: r271251 but it's part of a long series of patches (see PR89021) and I doubt it's backportable as-is.
[Bug target/89040] [9 Regressiom] Wrong code with -mno-mmx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89040 --- Comment #4 from Andrew Pinski --- (In reply to Hongtao.liu from comment #3) > > foo3b: > > .LFB0: > > .cfi_startproc > > movq%xmm0, %rax This should be "movd %xmm0, %eax". > > The issue can't be reproduced on current trunk. Right it seems like it was fixed in GCC 10.1.0. I have not looked into why though.
[Bug target/89040] [9 Regressiom] Wrong code with -mno-mmx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89040 --- Comment #3 from Hongtao.liu --- > foo3b: > .LFB0: > .cfi_startproc > movq%xmm0, %rax This should be "movd %xmm0, %eax". The issue can't be reproduced on current trunk.
[Bug target/89040] [9 Regressiom] Wrong code with -mno-mmx
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89040 Andrew Pinski changed: What|Removed |Added Known to fail||9.1.0, 9.4.0 Target Milestone|--- |9.5 Summary|Wrong code with -mno-mmx|[9 Regressiom] Wrong code ||with -mno-mmx Keywords||wrong-code Known to work||10.1.0, 8.5.0