[PATCHv6] Fix range end handling of inlined subroutines

[Bernd Edlinger]

Hi,

this is it, what might fix Luis aarch64 tests hopefully, please confirm.

It still misses a good test case, though.

I attached both the fixed version of my inline end patch,
and a diff of the test results:

 + is results with 3349112e380712432d5818154d67ab4660af056f.
 - is results with this patch applied to above version.

I often have a hard time to tell which is a regression and which is
just because of transient errors, where test cases are not stable.

I hope this also helps with the Problem that Andrew is tackling
in the other patch, since I keep at least some line-entries as is-stmt
which were previously just deleted, or converted to non-is-stmt,
that is what makes the issue from the patch description.

This changes only line table entries that are at the same PC as
an end of inline function block.  Exactly that is the information
that is missing in the DWARF format, therefore it is not possible
to just fix gcc IMHO, we must fix the DWARF format, thus create
a new version, implement that in gcc and in gdb, that should tell
us what to do with the line entries at these special places.

Andrew, could you try this, if this patch fixes your problem,
or at least does not make it harder to fix?


Thanks
Bernd.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Fix-range-end-handling-of-inlined-subroutines.patch
Type: text/x-patch
Size: 14600 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/gdb-patches/attachments/20200405/209d6c27/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: test.diff
Type: text/x-patch
Size: 30054 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/gdb-patches/attachments/20200405/209d6c27/attachment-0003.bin>