[Bug target/95112] New: i386 procedures have prolog endbr32

[Bug target/95112] New: i386 procedures have prolog endbr32

[akobets at mail dot ru]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95112

            Bug ID: 95112
           Summary: i386 procedures have prolog endbr32
           Product: gcc
           Version: 9.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: akobets at mail dot ru
  Target Milestone: ---

gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)

Test file:
===============
void test()
{
}
===============

Buld:
i686-linux-gnu-gcc -c -fno-PIC -mno-mmx -mno-sse -O2 -fomit-frame-pointer
-ffreestanding -fno-stack-protector --no-exceptions test.c

Result:
i686-linux-gnu-objdump -d test.o

test.o:     file format elf32-i386


disassembling section .text:

00000000 <test>:
   0:   f3 0f 1e fb             endbr32 
   4:   c3                      ret    
==============
Please help me find way to build clear code.
__attribute__((naked)) do not resolve problem.

[Bug target/95112] i686 procedures have prolog endbr32

[rguenth at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95112

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Try -fcf-protection=none

[Bug target/95112] i686 procedures have prolog endbr32

[akobets at mail dot ru]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95112

--- Comment #2 from Alexander Kobets <akobets at mail dot ru> ---
Yes, that it.
I am not sure, that CF must be enabled by default, at your discretion.
Thank you.

[Bug target/95112] i686 procedures have prolog endbr32

[sjames at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95112

Sam James <sjames at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID
                 CC|                            |sjames at gcc dot gnu.org

--- Comment #3 from Sam James <sjames at gcc dot gnu.org> ---
(In reply to Alexander Kobets from comment #2)
> Yes, that it.
> I am not sure, that CF must be enabled by default, at your discretion.
> Thank you.

I believe this is Ubuntu's patching of the specs, it doesn't happen upstream by
default.

It is possible (without making a commitment/official statement on it at all)
that one day --enable-standard-branch-protection might allow configuring this
for CET too but it doesn't right now.