[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 Jakub Jelinek changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 --- Comment #10 from CVS Commits --- The releases/gcc-8 branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:baef3efdc4992e4dcb7f4de62ff5bcb13bf05f60 commit r8-10016-gbaef3efdc4992e4dcb7f4de62ff5bcb13bf05f60 Author: Jakub Jelinek D

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 --- Comment #9 from CVS Commits --- The releases/gcc-9 branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:a91e5d88970c8d865a49f2a4ed4e17ee2c58b73f commit r9-8222-ga91e5d88970c8d865a49f2a4ed4e17ee2c58b73f Author: Jakub Jelinek Dat

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 --- Comment #8 from Kai Tietz --- Hmm, that behavior of gcc seems to be indeed pretty bad. The SEH commands for registers above index 15 (0..15) for xmm? are indeed undefined, and even worse, can't be coded proper into the seh table correctly. An

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 --- Comment #7 from CVS Commits --- The master branch has been updated by Jakub Jelinek : https://gcc.gnu.org/g:79ab8c4321b2dc940bb706a7432a530e26f0df1a commit r10-6522-g79ab8c4321b2dc940bb706a7432a530e26f0df1a Author: Jakub Jelinek Date: Sa

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 Agner Fog changed: What|Removed |Added CC||agner at agner dot org --- Comment #6 from A

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 --- Comment #5 from Daniel Fruzynski --- I got following link: https://stackoverflow.com/questions/53733624/is-xmm8-register-value-preserved-across-calls/53733767#53733767 Quote from it: "Any additional registers for newer instruction sets are v

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 --- Comment #4 from Daniel Fruzynski --- I have found that I can use -ffixed-reg option for this. It allows to eliminate one register, so I have to use it 16 times to eliminate all xmm16..31 registers. It would be handy to have another option whi

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 Daniel Fruzynski changed: What|Removed |Added CC||bugzilla@poradnik-webmaster

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 Jakub Jelinek changed: What|Removed |Added CC||jakub at gcc dot gnu.org --- Comment #2

[Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782 Kai Tietz changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|