[all-commits] [llvm/llvm-project] 83cdb6: [AArch64][Fix] LdSt optimization generate prematur...
dnsampaio via All-commits
all-commits at lists.llvm.org
Fri Mar 13 19:03:15 PDT 2020
Branch: refs/heads/master
Home: https://github.com/llvm/llvm-project
Commit: 83cdb654e4759ad00aba27f25615c4a0c7c2e62e
https://github.com/llvm/llvm-project/commit/83cdb654e4759ad00aba27f25615c4a0c7c2e62e
Author: Diogo Sampaio <Diogo.Sampaio at arm.com>
Date: 2020-03-14 (Sat, 14 Mar 2020)
Changed paths:
M llvm/lib/Target/AArch64/AArch64LoadStoreOptimizer.cpp
A llvm/test/CodeGen/AArch64/aarch64-ldst-no-premature-sp-pop.mir
M llvm/test/CodeGen/AArch64/arm64-nvcast.ll
M llvm/test/CodeGen/AArch64/arm64-windows-calls.ll
Log Message:
-----------
[AArch64][Fix] LdSt optimization generate premature stack-popping
Summary:
When moving add and sub to memory operand instructions,
aarch64-ldst-opt would prematurally pop the stack pointer,
before memory instructions that do access the stack using
indirect loads.
e.g.
```
int foo(int offset){
int local[4] = {0};
return local[offset];
}
```
would generate:
```
sub sp, sp, #16 ; Push the stack
mov x8, sp ; Save stack in register
stp xzr, xzr, [sp], #16 ; Zero initialize stack, and post-increment, making it invalid
------ If an exception goes here, the stack value might be corrupted
ldr w0, [x8, w0, sxtw #2] ; Access correct position, but it is not guarded by SP
```
Reviewers: fhahn, foad, thegameg, eli.friedman, efriedma
Reviewed By: efriedma
Subscribers: efriedma, kristof.beyls, hiraditya, danielkiss, llvm-commits, simon_tatham
Tags: #llvm
Differential Revision: https://reviews.llvm.org/D75755
More information about the All-commits
mailing list