diff options
author | David Spickett <david.spickett@linaro.org> | 2023-08-08 16:04:11 +0100 |
---|---|---|
committer | David Spickett <david.spickett@linaro.org> | 2023-08-31 10:21:53 +0100 |
commit | 6697afe99fb6df08d4c1903eb1df5446f2ec1993 (patch) | |
tree | ccb2a0e4e6c33022039499bbf7a950ef11e5dd47 /flang/lib/Frontend/CompilerInvocation.cpp | |
parent | 0407f681a7efa61f81f885e186c25ed99aecb8d4 (diff) | |
download | llvm-6697afe99fb6df08d4c1903eb1df5446f2ec1993.zip llvm-6697afe99fb6df08d4c1903eb1df5446f2ec1993.tar.gz llvm-6697afe99fb6df08d4c1903eb1df5446f2ec1993.tar.bz2 |
[lldb][AArch64] Check SIMD save/restore in SVE SIMD test
While doing some refactoring I forgot to carry over the copying in of
SIMD data in normal mode, but no tests failed.
Turns out, it's very easy for us to get the restore wrong because
even if you forget the memcopy, setting the buffer to valid may
just read the data you had before the expression evaluation.
So I've extended the SVE SIMD testing (which includes the plain SIMD mode)
to check expression save/restore. This is the only test that fails
if you forget to do `m_fpu_is_valid = true` so I take from that, that
prior to this it wasn't tested at all.
As a bonus, we now have coverage of the same thing for SVE and SSVE modes.
Reviewed By: omjavaid
Differential Revision: https://reviews.llvm.org/D157000
Diffstat (limited to 'flang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions