------- Comment #10 from acme at mandriva dot com 2006-11-14 17:19 ------- (In reply to comment #9) > > I'm quite aware of what GCC outputs here :) > > However, past the initial declarations, we don't output debug > information about what the state of the IR is at random points in the > compilation, only about what the final output looks like. Since there > is no inlined code left, we don't end up saying there is an inlined > subroutine. > > Even if we could change this, i'm not sure we'd want to. It doesn't > seem incorrect at all to do what we do. > Otherwise, you'd end up with inlined subroutine dies with no low > pc/high pc associated with them, which seems nonsensical.
OK, so I'll have to find another way of using the DWARF info to see if a inline routine, such as __task_rq_lock was used at all in the build or was just included in the DWARF info but not referenced anywhere, have to dig more into the available information... BTW, if, in these cases, DW_TAG_subroutine is not referenced, what is the purpose of it being included? Is there a reason my limited knowledge is not realising? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29792
