63eb7ff47d
This patch implements PAC return address signing for armv8-m. This patch roughly
accomplishes the following things:
- PAC and AUT instructions are generated.
- They're part of the stack frame setup, so that shrink-wrapping can move them
inwards to cover only part of a function
- The auth code generated by PAC is saved across subroutine calls so that AUT
can find it again to check
- PAC is emitted before stacking registers (so that the SP it signs is the one
on function entry).
- The new pseudo-register ra_auth_code is mentioned in the DWARF frame data
- With CMSE also in use: PAC is emitted before stacking FPCXTNS, and AUT
validates the corresponding value of SP
- Emit correct unwind information when PAC is replaced by PACBTI
- Handle tail calls correctly
Some notes:
We make the assembler accept the `.save {ra_auth_code}` directive that is
emitted by the compiler when it saves a register that contains a
return address authentication code.
For EHABI we need to have the `FrameSetup` flag on the instruction and
handle the `t2PACBTI` opcode (identically to `t2PAC`), so we can emit
`.save {ra_auth_code}`, instead of `.save {r12}`.
For PACBTI-M, the instruction which computes return address PAC should use SP
value before adjustment for the argument registers save are (used for variadic
functions and when a parameter is is split between stack and register), but at
the same it should be after the instruction that saves FPCXT when compiling a
CMSE entry function.
This patch moves the varargs SP adjustment after the FPCXT save (they are never
enabled at the same time), so in a following patch handling of the `PAC`
instruction can be placed between them.
Epilogue emission code adjusted in a similar manner.
PACBTI-M code generation should not emit any instructions for architectures
v6-m, v8-m.base, and for A- and R-class cores. Diagnostic message for such cases
is handled separately by a future ticket.
note on tail calls:
If the called function has four arguments that occupy registers `r0`-`r3`, the
only option for holding the function pointer itself is `r12`, but this register
is used to keep the PAC during function/prologue epilogue and clobbers the
function pointer.
When we do the tail call we need the five registers (`r0`-`r3` and `r12`) to
keep six values - the four function arguments, the function pointer and the PAC,
which is obviously impossible.
One option would be to authenticate the return address before all callee-saved
registers are restored, so we have a scratch register to temporarily keep the
value of `r12`. The issue with this approach is that it violates a fundamental
invariant that PAC is computed using CFA as a modifier. It would also mean using
separate instructions to pop `lr` and the rest of the callee-saved registers,
which would offset the advantages of doing a tail call.
Instead, this patch disables indirect tail calls when the called function take
four or more arguments and the return address sign and authentication is enabled
for the caller function, conservatively assuming the caller function would spill
LR.
This patch is part of a series that adds support for the PACBTI-M extension of
the Armv8.1-M architecture, as detailed here:
https://community.arm.com/arm-community-blogs/b/architectures-and-processors-blog/posts/armv8-1-m-pointer-authentication-and-branch-target-identification-extension
The PACBTI-M specification can be found in the Armv8-M Architecture Reference
Manual:
https://developer.arm.com/documentation/ddi0553/latest
The following people contributed to this patch:
- Momchil Velikov
- Ties Stuij
Reviewed By: danielkiss
Differential Revision: https://reviews.llvm.org/D112429
37 lines
1.3 KiB
ArmAsm
37 lines
1.3 KiB
ArmAsm
// RUN: not llvm-mc -triple=thumbv7 %s -o - 2>&1 | FileCheck %s --strict-whitespace
|
|
.text
|
|
.syntax unified
|
|
.code 16
|
|
.thumb_func
|
|
.global f
|
|
f:
|
|
.fnstart
|
|
.save {r11-ra_auth_code}
|
|
// CHECK: [[# @LINE - 1]]:16: error: pseudo-register not allowed
|
|
// CHECK-NEXT: .save {r11-ra_auth_code}
|
|
// CHECK-NEXT: ^
|
|
.save {r11, ra_auth_code, r12}
|
|
// CHECK: [[# @LINE - 1]]:31: warning: duplicated register (r12) in register list
|
|
// CHECK-NEXT: .save {r11, ra_auth_code, r12}
|
|
// CHECK-NEXT: ^
|
|
.save {ra_auth_code-r13}
|
|
// CHECK: [[# @LINE - 1]]:12: error: pseudo-register not allowed
|
|
// CHECK-NEXT: .save {ra_auth_code-r13}
|
|
// CHECK-NEXT: ^
|
|
push {ra_auth_code}
|
|
// CHECK: [[# @LINE - 1]]:11: error: pseudo-register not allowed
|
|
// CHECK-NEXT: push {ra_auth_code}
|
|
// CHECK-NEXT: ^
|
|
push {r11, ra_auth_code}
|
|
// CHECK: [[# @LINE - 1]]:16: error: pseudo-register not allowed
|
|
// CHECK-NEXT: push {r11, ra_auth_code}
|
|
// CHECK-NEXT: ^
|
|
push {ra_auth_code, r12}
|
|
// CHECK: [[# @LINE - 1]]:11: error: pseudo-register not allowed
|
|
// CHECK-NEXT: push {ra_auth_code, r12}
|
|
// CHECK-NEXT: ^
|
|
push {ra_auth_code, r13}
|
|
// CHECK: [[# @LINE - 1]]:11: error: pseudo-register not allowed
|
|
// CHECK-NEXT: push {ra_auth_code, r13}
|
|
// CHECK-NEXT: ^
|