[Bug ld/29263] New: /usr/bin/ld: warning: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/crtn.o: missing .note.GNU-stack section implies executable stack

[danglin at gcc dot gnu.org]

https://sourceware.org/bugzilla/show_bug.cgi?id=29263

            Bug ID: 29263
           Summary: /usr/bin/ld: warning:
                    /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu
                    /crtn.o: missing .note.GNU-stack section implies
                    executable stack
           Product: binutils
           Version: 2.39 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: ld
          Assignee: unassigned at sourceware dot org
          Reporter: danglin at gcc dot gnu.org
                CC: nickc at sourceware dot org
  Target Milestone: ---
              Host: hppa*-*-linux*
            Target: hppa*-*-linux*
             Build: hppa*-*-linux*

int main(void) { return 0; }

dave@mx3210:~/shmat$ gcc main.c
/usr/bin/ld: warning:
/usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/crtn.o: missing
.note.GNU-stack section implies executable stack
/usr/bin/ld: NOTE: This behaviour is deprecated and will be removed in a future
version of the linker
/usr/bin/ld: warning: a.out has a LOAD segment with RWX permissions

The first warning seems bogus as crtn.o is not an executable file.

On hppa-linux with kernel v5.18 and later, we don't need an executable
stack for signal support but we still need it for gcc nested functions.

As far as I can tell, an executable stack is still the default in glibc
for many targets.

-- 
You are receiving this mail because:
You are on the CC list for the bug.