diff options
| author | Alexandros Lamprineas <alexandros.lamprineas@arm.com> | 2021-09-02 12:48:07 +0100 |
|---|---|---|
| committer | Alexandros Lamprineas <alexandros.lamprineas@arm.com> | 2021-09-16 12:56:43 +0100 |
| commit | 61f25daa8d1b69dd5138facd5d57a8e3dfa0c5cc (patch) | |
| tree | 584720a6476618478703fd9666e09ef9f971d20f /llvm/lib/CodeGen/CommandFlags.cpp | |
| parent | 054e331d9dbd3ce98b19625b75ba38dd9ebc34cc (diff) | |
| download | llvm-61f25daa8d1b69dd5138facd5d57a8e3dfa0c5cc.zip llvm-61f25daa8d1b69dd5138facd5d57a8e3dfa0c5cc.tar.gz llvm-61f25daa8d1b69dd5138facd5d57a8e3dfa0c5cc.tar.bz2 | |
[ARM][CMSE] Clear the secure fp-registers when using softfp abi.
When expanding the non-secure call instruction we are emiting code
to clear the secure floating-point registers only if the targeted
architecture has floating-point support. The potential problem is
when the source code containing non-secure calls are built with
-mfloat-abi=soft but some other part of the system has been built
with -mfloat-abi=softfp (soft and softfp are compatible as they use
the same procedure calling standard). In this case floating-point
registers could leak to non-secure state as the non-secure won't
have cleared them assuming no floating point has been used.
Differential Revision: https://reviews.llvm.org/D109153
Diffstat (limited to 'llvm/lib/CodeGen/CommandFlags.cpp')
0 files changed, 0 insertions, 0 deletions