[Bug target/96350] [cet] For ENDBR immediate, the binary would include a gadget that starts with a fake ENDBR64 opcode.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96350 Hongtao.liu changed: What|Removed |Added Resolution|--- |FIXED Status|NEW

[Bug target/96350] [cet] For ENDBR immediate, the binary would include a gadget that starts with a fake ENDBR64 opcode.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96350 --- Comment #5 from CVS Commits --- The master branch has been updated by hongtao Liu : https://gcc.gnu.org/g:9a5381f749ee2cef51af67895de182113e45f642 commit r11-2716-g9a5381f749ee2cef51af67895de182113e45f642 Author: liuhongt Date: Tue Aug

[Bug target/96350] [cet] For ENDBR immediate, the binary would include a gadget that starts with a fake ENDBR64 opcode.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96350 --- Comment #4 from H.J. Lu --- Created attachment 48944 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48944=edit An experimental patch

[Bug target/96350] [cet] For ENDBR immediate, the binary would include a gadget that starts with a fake ENDBR64 opcode.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96350 --- Comment #3 from Richard Biener --- The endbr are way too short to make this practical - ISTR I raised this exact issue at a presentation about CET ... CET simply makes the gadget finding less likely to succeed. There's always the

[Bug target/96350] [cet] For ENDBR immediate, the binary would include a gadget that starts with a fake ENDBR64 opcode.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96350 --- Comment #2 from H.J. Lu --- We can force 0xfa1e0ff3 into memory with [hjl@gnu-snb-1 tmp]$ cat bar.s .text .p2align 4 .globl foo .type foo, @function foo: movl.LC0(%rip), %eax ret

[Bug target/96350] [cet] For ENDBR immediate, the binary would include a gadget that starts with a fake ENDBR64 opcode.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96350 H.J. Lu changed: What|Removed |Added Last reconfirmed||2020-07-28 Ever confirmed|0