[llvm-bugs] [Bug 45040] New: -gdwarf-5 and binutils 2.30 compat

via llvm-bugs llvm-bugs at lists.llvm.org
Wed Feb 26 20:14:14 PST 2020


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

            Bug ID: 45040
           Summary: -gdwarf-5 and binutils 2.30 compat
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: DebugInfo
          Assignee: unassignedbugs at nondot.org
          Reporter: ndesaulniers at google.com
                CC: jdevlieghere at apple.com, keith.walker at arm.com,
                    llvm-bugs at lists.llvm.org,
                    paul_robinson at playstation.sony.com, srhines at google.com
            Blocks: 4068

I'm trying to use `-gdwarf-5 -no-integrated-as` to enable dwarf-5 support in
the Linux kernel, and running into issues with my assembler, GNU as 2.30.

do_mounts.s:19: Error: junk at end of line, first unrecognized character is `m'
do_mounts.s:19: Error: file number less than one

Looks like the following line:

  .file 0 "/home/nick/linux/init/do_mounts.c" md5
0x62e8a195aa9d4d8b466f84b7775ea4cd

So it looks like a file index starting from 0 is problematic, AND the md5
checksums are problematic.

Are there flags to disable these?  I know I should just update my binutils, but
it would be nice to still support a few releases of GNU binutils, if possible.

https://sourceware.org/binutils/docs/as/File.html#File for example states:
`The fileno operand should be a unique positive integer`.

The checksums don't seem documented in binutils docs (at least for the .file
directive), and I haven't yet looked at their source or newer versions to see
if this is supported.


Referenced Bugs:

https://bugs.llvm.org/show_bug.cgi?id=4068
[Bug 4068] [Meta] Compiling the Linux kernel with clang
-- 
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/20200227/91f6a72d/attachment.html>


More information about the llvm-bugs mailing list