https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94649
--- Comment #7 from Henning Baldersheim ---
Thanks, perhaps add 104688 to the see also list.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94649
--- Comment #5 from Henning Baldersheim ---
Are there any next steps here.
This is still an issue at least with gcc-12. It would be nice to get rid of the
hacks we have to avoid it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108599
--- Comment #10 from Henning Baldersheim ---
Will this be backported to gcc-12, or do we need to wait for gcc-13 ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108599
--- Comment #2 from Henning Baldersheim ---
This is an even bigger issue with gcc 13. Then it only requires -march=haswell
Works:
c++ -Wall -Wextra -O3 -march=ivybridge test.cpp && ./a.out
Fails:
c++ -Wall -Wextra -O3 -march=haswell test.cpp &
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108599
--- Comment #1 from Henning Baldersheim ---
This is spun out from https://github.com/vespa-engine/vespa/pull/25786
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108599
Bug ID: 108599
Summary: Incorrect code generation newer intel architectures
for gcc 12 and 13
Product: gcc
Version: 12.1.1
Status: UNCONFIRMED
Severity: normal
