aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/gdbclientutils.py
diff options
context:
space:
mode:
authorAnatoly Trosinenko <atrosinenko@accesssoftek.com>2025-06-25 13:11:23 +0300
committerGitHub <noreply@github.com>2025-06-25 13:11:23 +0300
commita8a2c6fa882d8e3956cd189ff9f654bf91ced4b1 (patch)
tree73216cd33110d3261f076a663b897e955b132da5 /lldb/packages/Python/lldbsuite/test/gdbclientutils.py
parent36a060a4e51b09f4cd6dc41bc8d82c8dd22084df (diff)
downloadllvm-a8a2c6fa882d8e3956cd189ff9f654bf91ced4b1.zip
llvm-a8a2c6fa882d8e3956cd189ff9f654bf91ced4b1.tar.gz
llvm-a8a2c6fa882d8e3956cd189ff9f654bf91ced4b1.tar.bz2
[BOLT] Gadget scanner: fix LR to be safe in leaf functions without CFG (#141824)
After a label in a function without CFG information, use a reasonably pessimistic estimation of register state (assume that any register that can be clobbered in this function was actually clobbered) instead of the most pessimistic "all registers are unsafe". This is the same estimation as used by the dataflow variant of the analysis when the preceding instruction is not known for sure. Without this, leaf functions without CFG information are likely to have false positive reports about non-protected return instructions, as 1) LR is unlikely to be signed and authenticated in a leaf function and 2) LR is likely to be used by a return instruction near the end of the function and 3) the register state is likely to be reset at least once during the linear scan through the function
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/gdbclientutils.py')
0 files changed, 0 insertions, 0 deletions