aboutsummaryrefslogtreecommitdiff
path: root/test-driver
diff options
context:
space:
mode:
authorGuinevere Larsen <blarsen@redhat.com>2023-11-01 17:25:32 +0100
committerGuinevere Larsen <blarsen@redhat.com>2024-01-02 10:21:37 +0100
commit528b729be1a293a21f44149351f3eba5b4e2d870 (patch)
tree3959ec9a424c769dfeffe89440fc4c6165df3916 /test-driver
parentb22ee0e49ba2bac8a5295f0426c62e9bd2b311a1 (diff)
downloadgdb-528b729be1a293a21f44149351f3eba5b4e2d870.zip
gdb-528b729be1a293a21f44149351f3eba5b4e2d870.tar.gz
gdb-528b729be1a293a21f44149351f3eba5b4e2d870.tar.bz2
gdb/dwarf2: Add support for DW_LNS_set_epilogue_begin in line-table
This commit adds a mechanism for GDB to detect the linetable opcode DW_LNS_set_epilogue_begin. This opcode is set by compilers to indicate that a certain instruction marks the point where the frame is destroyed. While the standard allows for multiple points marked with epilogue_begin in the same function, for performance reasons, the function that searches for the epilogue address will only find the last address that sets this flag for a given block. This commit also changes amd64_stack_frame_destroyed_p_1 to attempt to use the epilogue begin directly, and only if an epilogue can't be found will it attempt heuristics based on the current instruction. Finally, this commit also changes the dwarf assembler to be able to emit epilogue-begin instructions, to make it easier to test this patch Approved-By: Tom Tromey <tom@tromey.com>
Diffstat (limited to 'test-driver')
0 files changed, 0 insertions, 0 deletions