Re: PROPOSAL: augmentation for "thin" inlines

[David B Anderson <davea at quasar dot engr dot sgi dot com>]

Todd Allen writes:
> | An inlined subroutine entry may also have DW_AT_call_file,
> | DW_AT_call_line, DW_AT_call_column attributes, each of whose value is an
> | integer constant.  These attributes represent the source file, source
> | line number, and source column number, respectively, of the first
> | character of the statement or expression that caused the inline expansion.
> | They should not refer to declaration coordinates of the original
> | declaration, but rather to those of the point at which it was inlined.
> | The DW_AT_call_file attribute corresponds to a file number from the
> | statement information table for the compilation unit containing the
> | debugging information entry, just as the DW_AT_decl_file attribute does.


What gets put in DW_AT_call_line in a nested-2-deep inlined
subroutine?  The DW_AT_call_line of the non-inlined-code or
the line of the inlined-caller?
I don't find this question answered in the proposal... did I miss something?


davea@sgi.com