d391e4fe84
Be more consistent in the naming convention for the various RET instructions to specify in terms of bitwidth. Helps prevent future scheduler model mismatches like those that were only addressed in D44687. Differential Revision: https://reviews.llvm.org/D113302
31 lines
621 B
YAML
31 lines
621 B
YAML
# RUN: not llc -march=x86-64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
|
|
--- |
|
|
|
|
define i32 @test(i32 %a) #0 {
|
|
entry:
|
|
%b = alloca i32
|
|
store i32 %a, i32* %b
|
|
%c = load i32, i32* %b
|
|
ret i32 %c
|
|
}
|
|
|
|
attributes #0 = { "frame-pointer"="none" }
|
|
|
|
...
|
|
---
|
|
name: test
|
|
frameInfo:
|
|
maxAlignment: 4
|
|
fixedStack:
|
|
# CHECK: [[@LINE+1]]:52: unknown key 'isImmutable'
|
|
- { id: 0, type: spill-slot, offset: 0, size: 4, isImmutable: true }
|
|
stack:
|
|
- { id: 0, offset: -12, size: 4, alignment: 4 }
|
|
body: |
|
|
bb.0.entry:
|
|
MOV32mr %rsp, 1, _, -4, _, %edi
|
|
%eax = COPY %edi
|
|
RET64 %eax
|
|
...
|