[llvm-bugs] [Bug 42008] New: Support for .gnu.warning. section to generate linker warnings

via llvm-bugs llvm-bugs at lists.llvm.org
Fri May 24 09:20:18 PDT 2019


https://bugs.llvm.org/show_bug.cgi?id=42008

            Bug ID: 42008
           Summary: Support for .gnu.warning. section to generate linker
                    warnings
           Product: lld
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: ELF
          Assignee: unassignedbugs at nondot.org
          Reporter: arichardson.kde at gmail.com
                CC: llvm-bugs at lists.llvm.org, peter.smith at linaro.org

I recently tried to use the .gnu.warning mechanism with LLD and noticed that it
is not supported.

If I try the example from
http://ninjalj.blogspot.com/2011/11/your-own-linker-warnings-using-gnu.html, I
only get output with ld.bfd.
$ $LLVM_BUILD/bin/clang -fuse-ld=$LLVM_BUILD/bin/ld.lld -o linkwarn linkwarn.o
linkwarnmain.o
 (no output)
$ $LLVM_BUILD/bin/clang -fuse-ld=/usr/bin/ld.bfd -o linkwarn linkwarn.o
linkwarnmain.o
linkwarnmain.o: In function `main':
linkwarnmain.c:(.text+0x10): warning: foo is deprecated, please use the shiny
new foobar function

Looking for .gnu.warning in the source tree, I can only find references in
llvm-objcopy. Is this a feature that should be supported in LLD?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190524/b2bb82eb/attachment.html>


More information about the llvm-bugs mailing list