[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #19 from CVS Commits --- The releases/gcc-9 branch has been updated by H.J. Lu : https://gcc.gnu.org/g:5ed78f8bd84eb696579d928c816bc840664829b2 commit r9-9792-g5ed78f8bd84eb696579d928c816bc840664829b2 Author: H.J. Lu Date: Thu Oc

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #18 from CVS Commits --- The releases/gcc-10 branch has been updated by H.J. Lu : https://gcc.gnu.org/g:523dc71f5cb858da18e1f648269746dab519b445 commit r10-10228-g523dc71f5cb858da18e1f648269746dab519b445 Author: H.J. Lu Date: Thu

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #17 from CVS Commits --- The releases/gcc-11 branch has been updated by H.J. Lu : https://gcc.gnu.org/g:e74336df42fa36244d576dd155d7e2e2c42bc3a0 commit r11-9179-ge74336df42fa36244d576dd155d7e2e2c42bc3a0 Author: H.J. Lu Date: Thu

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #16 from CVS Commits --- The master branch has been updated by H.J. Lu : https://gcc.gnu.org/g:1373066a46d8d47abd97e46a005aef3b3dbfe94a commit r12-4619-g1373066a46d8d47abd97e46a005aef3b3dbfe94a Author: H.J. Lu Date: Thu Oct 21 09

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #15 from Martin Liška --- (In reply to H.J. Lu from comment #14) > (In reply to Martin Liška from comment #13) > > @H.J. Can you please document that one needs at least i686 CPU for the > > functionality? > > Like this? > > diff --g

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #14 from H.J. Lu --- (In reply to Martin Liška from comment #13) > @H.J. Can you please document that one needs at least i686 CPU for the > functionality? Like this? diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi index c66a2

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 Martin Liška changed: What|Removed |Added CC||marxin at gcc dot gnu.org --- Comment #13

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 H.J. Lu changed: What|Removed |Added Target Milestone|--- |11.0 Status|NEW

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 Bug 98667 depends on bug 70454, which changed state. Bug 70454 Summary: --with-arch=native isn't applied to 32-bit x86 target library https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70454 What|Removed |Added --

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #11 from Matthew Whitehead --- A patch has been proposed to remove the -fcf-protection=full from the ebuild script: https://bugs.gentoo.org/765442

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #10 from H.J. Lu --- (In reply to Matthew Whitehead from comment #1) > Here is the full set of compiler flags used. > > readelf --string-dump='.GCC.command.line' /usr/lib/debug/$( which eix > ).debug > > String dump of section '.G

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #9 from CVS Commits --- The master branch has been updated by H.J. Lu : https://gcc.gnu.org/g:77d372abec0fbf2cfe922e3140ee3410248f979e commit r11-6672-g77d372abec0fbf2cfe922e3140ee3410248f979e Author: H.J. Lu Date: Thu Jan 14 05:

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #8 from H.J. Lu --- (In reply to Richard Biener from comment #6) > It probably makes sense to disable CET by default when GCC is configured to > "less" than i686-linux (definitely for i386 and i486, not sure about i586). > Thus change

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #7 from H.J. Lu --- A patch is posted at https://gcc.gnu.org/pipermail/gcc-patches/2021-January/563478.html

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 Richard Biener changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

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

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #4 from Matthew Whitehead --- It looks like /usr/bin/gdb 10.1 also has this opcode in it: objdump -D /usr/bin/gdb | grep -B6 -A6 endbr32 60d7b5: 3f aas 60d7b6: 1a 3b sbb

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #3 from Matthew Whitehead --- This is on an actual first generation i486DX 40MHz system I use to test for code issues exactly like this case.

[Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667 --- Comment #2 from Andrew Pinski --- Is this directly on a i486 box or VirtualBox? VirtualBox might have a bug.