[Bug debug/67163] New: g2 generates incorrect decl_line

[Bug debug/67163] New: g2 generates incorrect decl_line

[dehao at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67163

            Bug ID: 67163
           Summary: g2 generates incorrect decl_line
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: debug
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dehao at gcc dot gnu.org
  Target Milestone: ---

#g++ -c -o ValueStore.o   -O2 -g1        ValueStore.ii
#objdump --dwarf=info ValueStore.o|grep -A 2 isDuplicateOf
    <615>   DW_AT_name        : (indirect string, offset: 0x490): isDuplicateOf
    <619>   DW_AT_decl_file   : 11
    <61a>   DW_AT_decl_line   : 297

#g++ -c -o ValueStore.o   -O2 -g2        ValueStore.ii
#objdump --dwarf=info ValueStore.o|grep -A 2 isDuplicateOf
    <5114>   DW_AT_name        : (indirect string, offset: 0x563d):
isDuplicateOf
    <5118>   DW_AT_decl_file   : 51
    <5119>   DW_AT_decl_line   : 150

g1 generates correct decl_line, but g2 generates incorrect decl_line (150 is
the decl_line for another function: addValue)

[Bug debug/67163] g2 generates incorrect decl_line

[dehao at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67163

--- Comment #1 from dehao at gcc dot gnu.org ---
Created attachment 36157
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36157&action=edit
preprocessed file

[Bug debug/67163] g2 generates incorrect decl_line

[dehao at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67163

--- Comment #2 from dehao at gcc dot gnu.org ---
Created attachment 36158
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36158&action=edit
preprocessed file

[Bug debug/67163] g2 generates incorrect decl_line

[dehao at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67163

--- Comment #4 from dehao at gcc dot gnu.org ---
Right, in -g2 binary debug info, the decl_file is pointing to the header file
in which the function is declared. However, if the definition is available, it
makes more sense to point decl_file and decl_line where it's actually defined,
right? Additionally, it's better to keep g1 and g2 debug info consistent.