aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorBenjamin Maxwell <benjamin.maxwell@arm.com>2025-10-14 09:31:20 +0100
committerGitHub <noreply@github.com>2025-10-14 09:31:20 +0100
commit400faf912e40c17c79f58fd5d599fc9268221466 (patch)
tree73c8766812dab0355fde322d9e9af4313b51bbbd /lldb/packages/Python/lldbsuite/test
parentd49aa40fc703d061f48e520b9c1b63e6646c6907 (diff)
downloadllvm-400faf912e40c17c79f58fd5d599fc9268221466.zip
llvm-400faf912e40c17c79f58fd5d599fc9268221466.tar.gz
llvm-400faf912e40c17c79f58fd5d599fc9268221466.tar.bz2
[AArch64][SME] Treat agnostic ZA invokes like private ZA callees (#162684)
An invoke of an agnostic ZA function behaves like a private ZA callee. If the invoke does not return normally (and we end up in an exception block in the caller), ZA must be committed to the caller's save buffer (and off). We can ensure this by setting up a ZA save before an agnostic ZA invoke. This will result in the agnostic ZA invoke committing ZA to its caller's save buffer, rather than its local buffer, which allows us to reload the correct contents of ZA within exception blocks. Note: This also means we must restore ZA on the non-exceptional path from the `invoke` (since ZA could have been committed to the save buffer in either case).
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
0 files changed, 0 insertions, 0 deletions