[prev in list] [next in list] [prev in thread] [next in thread] 

List:       binutils-bugs
Subject:    [Bug gas/25614] New: dwarf-5 allows for .file 0
From:       "ndesaulniers at google dot com" <sourceware-bugzilla () sourceware ! org>
Date:       2020-02-28 22:55:59
Message-ID: bug-25614-70 () http ! sourceware ! org/bugzilla/
[Download RAW message or body]

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

            Bug ID: 25614
           Summary: dwarf-5 allows for .file 0
           Product: binutils
           Version: 2.35 (HEAD)
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gas
          Assignee: unassigned at sourceware dot org
          Reporter: ndesaulniers at google dot com
  Target Milestone: ---

.file 0 "asdf"
.section .debug_info,"",@progbits
.long 3
.short 5

$ as x.s 
x.s: Assembler messages:
x.s:1: Error: file number less than one

It seems that dwarf-5 may have added support for `0` as a valid file number. 
Clang warns:

$ clang x.s -c
x.s:1:1: warning: file 0 not supported prior to DWARF-5
.file 0 "asdf"
^
$ clang x.s -c -gdwarf-5

I *think* section "2.14 Declaration Coordinates" pdf page 68 of [0] addresses
this:
"The value 0 indicates that no source file has been specified."

See also [1].

[0] http://www.dwarfstd.org/doc/DWARF5.pdf
[1] https://bugs.llvm.org/show_bug.cgi?id=45040

-- 
You are receiving this mail because:
You are on the CC list for the bug.
[prev in list] [next in list] [prev in thread] [next in thread]