summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/context-object-objc
diff options
context:
space:
mode:
authorPeter Collingbourne <peter@pcc.me.uk>2019-06-22 00:06:51 +0000
committerPeter Collingbourne <peter@pcc.me.uk>2019-06-22 00:06:51 +0000
commit4608868d2f4c074269fdb766c2d79c9513ed4ae9 (patch)
tree432485824cef5917d42b40aefeb44dfebf51a4fc /lldb/packages/Python/lldbsuite/test/expression_command/context-object-objc
parent21f0f7170670d8d8d04376ee6309022f8228b796 (diff)
downloadbcm5719-llvm-4608868d2f4c074269fdb766c2d79c9513ed4ae9.tar.gz
bcm5719-llvm-4608868d2f4c074269fdb766c2d79c9513ed4ae9.zip
AArch64: Prefer FP-relative debug locations in HWASANified functions.
To help produce better diagnostics for stack use-after-return, we'd like to be able to determine the addresses of each HWASANified function's local variables given a small amount of information recorded on entry to the function. Currently we require all HWASANified functions to use frame pointers and record (PC, FP) on function entry. This works better than recording SP because FP cannot change during the function, unlike SP which can change e.g. due to dynamic alloca. However, most variables currently end up using SP-relative locations in their debug info. This prevents us from recomputing the address of most variables because the distance between SP and FP isn't recorded in the debug info. To address this, make the AArch64 backend prefer FP-relative debug locations when producing debug info for HWASANified functions. Differential Revision: https://reviews.llvm.org/D63300 llvm-svn: 364117
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/context-object-objc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud