[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
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.
[Bug ld/29263] /usr/bin/ld: warning: /usr/lib/gcc/hppa-linux-gnu/11/../../../hppa-linux-gnu/crtn.o: missing .note.GNU-stack section implies executable stack
https://sourceware.org/bugzilla/show_bug.cgi?id=29263 --- Comment #1 from John David Anglin --- dave@mx3210:~/gnu/binutils/src$ ld --version GNU ld (GNU Binutils for Debian) 2.38.50.20220615 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29262] A Potential Memory Leak Bug
https://sourceware.org/bugzilla/show_bug.cgi?id=29262 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0d02e70b197c786f26175b9a73f94e01d14abdab commit 0d02e70b197c786f26175b9a73f94e01d14abdab Author: Alan Modra Date: Mon Jun 20 10:39:31 2022 +0930 PR29262, memory leak in pr_function_type PR 29262 * prdbg.c (pr_function_type): Free "s" on failure path. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29261] A Potential Memory Leak Bug
https://sourceware.org/bugzilla/show_bug.cgi?id=29261 --- Comment #1 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Alan Modra : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8a24927bc8dbf6beac2000593b21235c3796dc35 commit 8a24927bc8dbf6beac2000593b21235c3796dc35 Author: Alan Modra Date: Mon Jun 20 10:39:13 2022 +0930 PR29261, memory leak in parse_stab_struct_fields PR 29261 * stabs.c (parse_stab_struct_fields): Free "fields" on failure path. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29261] A Potential Memory Leak Bug
https://sourceware.org/bugzilla/show_bug.cgi?id=29261 Alan Modra changed: What|Removed |Added Target Milestone|--- |2.39 Assignee|unassigned at sourceware dot org |amodra at gmail dot com Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Alan Modra --- Fixed. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug binutils/29262] A Potential Memory Leak Bug
https://sourceware.org/bugzilla/show_bug.cgi?id=29262 Alan Modra changed: What|Removed |Added Assignee|unassigned at sourceware dot org |amodra at gmail dot com Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Target Milestone|--- |2.39 --- Comment #2 from Alan Modra --- Fixed. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gas/29256] A Potential Memory Leak Bug
https://sourceware.org/bugzilla/show_bug.cgi?id=29256 Alan Modra changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Target Milestone|--- |2.39 --- Comment #3 from Alan Modra --- I think this is the best we can do here, closing. -- You are receiving this mail because: You are on the CC list for the bug.