[Bug ld/31067] symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
https://sourceware.org/bugzilla/show_bug.cgi?id=31067 --- Comment #2 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1c320501655ec8d5077d0a3231652c7d661249bc commit 1c320501655ec8d5077d0a3231652c7d661249bc Author: Nick Clifton Date: Tue Nov 21 09:26:19 2023 + Fix: symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM PR 31067 * linker.c (_bfd_generic_link_add_one_symbol): When issuing a warning message, also display a message about the warning not being affected by garbage colleciton. * ld.texi (Special Sections): New entry in the linker manual. Describes how the .gnu.warning and .gnu.warning.SYM sections behave. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31067] symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
https://sourceware.org/bugzilla/show_bug.cgi?id=31067 Nick Clifton changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Nick Clifton --- I could not find a simple way to postpone issuing the warning message until after garbage collection. So instead I have applied a patch that does two things: Firstly it adds an extra line after the warning message is displayed (if garbage collection has been enabled). So for example the bug demonstrator attached to this PR now produces this output: ld: test.o: in function `f': test.c:(.text.unused+0xa): warning: This shouldn't be emitted with --gc-sections ld: test.o: note: the message above does not take linker garbage collection into account Secondly I have created a new section in the linker manual to document the behaviour of the .gnu.warning and .gnu.warning.SYM sections: When linking ELF format object files 'ld' treats some sections in a special, non standard manner. This part of the manual describes these sections. '.gnu.warning' The contents of any section with this name are assumed to be an ascii format warning message. The contents will be displayed to the user if the sections appears in any input file, but the section will not be copied into the output image. If the '--fatal-warnings' option is enabled then the warnings - if any are encountered - will also stop the link from completing. Note - the '.gnu.warning' section is not subject to linker garbage collection or orphan handling. '.gnu.warning.SYM' The contents of any section whoes name starts with the prefix '.gnu.warning.' and then finishes with the name of a symbol is treated in a similar fashion to the '.gnu.warning' section, but only if the named symbol is defined. So for example the contents of a section called '.gnu.warning.foo' will be displayed as warning message if, and only if, the symbol 'foo' is defined by one or more of the input files. This includes object files pulled in from static libraries, shared objects needed to complete the link and so on. Note - because these warning messages are generated before the linker performs garbage collection (if enabled) it is possible for a warning to be displayed for a symbol that is later removed and then never appears in the final output. I am setting the status to RESOLVED/FIXED even though that is not really accurate. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31067] symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
https://sourceware.org/bugzilla/show_bug.cgi?id=31067 --- Comment #4 from Richard Earnshaw --- Prior to the patch you've just installed the only documentation for this feature that I've been able to find (other than the patch itself) is the NEWS entry. That reads: * When an ELF section named .gnu.warning.SYMBOL is encountered in an input file, and the symbol SYMBOL is referenced by some object file, the contents of ^^ the section are displayed as an error message. But your patch talks about SYMBOL being defined. The two are quite different, so which is correct? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31067] symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
https://sourceware.org/bugzilla/show_bug.cgi?id=31067 --- Comment #5 from cvs-commit at gcc dot gnu.org --- The master branch has been updated by Nick Clifton : https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=1367eeec2cbd1bb14b89030e199d06fc676ffc49 commit 1367eeec2cbd1bb14b89030e199d06fc676ffc49 Author: Nick Clifton Date: Tue Nov 21 11:30:03 2023 + Fix: symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM PR 31067 Fix typo in previous delta: defined -> referenced. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug ld/31067] symbols eliminated by --gc-sections still trigger warnings for gnu.warning.SYM
https://sourceware.org/bugzilla/show_bug.cgi?id=31067 --- Comment #6 from Nick Clifton --- (In reply to Richard Earnshaw from comment #4) > But your patch talks about SYMBOL being defined. The two are quite > different, so which is correct? *sigh* The NEWS file is correct. I was obviously not thinking clearly when I wrote the documentation. Sorry. I have checked in a patch to correct this mistake. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30889] can't compile without large file support
https://sourceware.org/bugzilla/show_bug.cgi?id=30889 Kurt Goebel changed: What|Removed |Added CC||kurt.goebel at oracle dot com Priority|P2 |P3 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug gprofng/30893] gprofng uses syscall + perf_event (hwcdrv) and ptrace (gpcollect) without any check and doc
https://sourceware.org/bugzilla/show_bug.cgi?id=30893 Kurt Goebel changed: What|Removed |Added CC||kurt.goebel at oracle dot com Priority|P2 |P3 -- You are receiving this mail because: You are on the CC list for the bug.
