mirror of
https://github.com/c64scene-ar/llvm-6502.git
synced 2024-12-15 20:29:48 +00:00
7c9c6ed761
Essentially the same as the GEP change in r230786.
A similar migration script can be used to update test cases, though a few more
test case improvements/changes were required this time around: (r229269-r229278)
import fileinput
import sys
import re
pat = re.compile(r"((?:=|:|^)\s*load (?:atomic )?(?:volatile )?(.*?))(| addrspace\(\d+\) *)\*($| *(?:%|@|null|undef|blockaddress|getelementptr|addrspacecast|bitcast|inttoptr|\[\[[a-zA-Z]|\{\{).*$)")
for line in sys.stdin:
sys.stdout.write(re.sub(pat, r"\1, \2\3*\4", line))
Reviewers: rafael, dexonsmith, grosser
Differential Revision: http://reviews.llvm.org/D7649
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@230794 91177308-0d34-0410-b5e6-96231b3b80d8
61 lines
1.6 KiB
LLVM
61 lines
1.6 KiB
LLVM
; RUN: llc -verify-machineinstrs < %s -mtriple=aarch64-none-linux-gnu | FileCheck %s
|
|
; RUN: llc -verify-machineinstrs < %s -mtriple=aarch64-none-linux-gnu -disable-fp-elim | FileCheck -check-prefix CHECK-WITHFP-ARM64 %s
|
|
|
|
; Make sure a reasonably sane prologue and epilogue are
|
|
; generated. This test is not robust in the face of an frame-handling
|
|
; evolving, but still has value for unrelated changes, I
|
|
; believe.
|
|
;
|
|
; In particular, it will fail when ldp/stp are used for frame setup,
|
|
; when FP-elim is implemented, and when addressing from FP is
|
|
; implemented.
|
|
|
|
@var = global i64 0
|
|
@local_addr = global i64* null
|
|
|
|
declare void @foo()
|
|
|
|
define void @trivial_func() nounwind {
|
|
; CHECK-LABEL: trivial_func: // @trivial_func
|
|
; CHECK-NEXT: // BB#0
|
|
; CHECK-NEXT: ret
|
|
|
|
ret void
|
|
}
|
|
|
|
define void @trivial_fp_func() {
|
|
; CHECK-WITHFP-AARCH64-LABEL: trivial_fp_func:
|
|
; CHECK-WITHFP-AARCH64: sub sp, sp, #16
|
|
; CHECK-WITHFP-AARCH64: stp x29, x30, [sp]
|
|
; CHECK-WITHFP-AARCH64-NEXT: mov x29, sp
|
|
|
|
; CHECK-WITHFP-ARM64-LABEL: trivial_fp_func:
|
|
; CHECK-WITHFP-ARM64: stp x29, x30, [sp, #-16]!
|
|
; CHECK-WITHFP-ARM64-NEXT: mov x29, sp
|
|
|
|
; Dont't really care, but it would be a Bad Thing if this came after the epilogue.
|
|
; CHECK: bl foo
|
|
call void @foo()
|
|
ret void
|
|
|
|
; CHECK-WITHFP: ldp x29, x30, [sp]
|
|
; CHECK-WITHFP: add sp, sp, #16
|
|
|
|
; CHECK-WITHFP: ret
|
|
}
|
|
|
|
define void @stack_local() {
|
|
%local_var = alloca i64
|
|
; CHECK-LABEL: stack_local:
|
|
; CHECK: sub sp, sp, #16
|
|
|
|
%val = load i64, i64* @var
|
|
store i64 %val, i64* %local_var
|
|
; CHECK-DAG: str {{x[0-9]+}}, [sp, #{{[0-9]+}}]
|
|
|
|
store i64* %local_var, i64** @local_addr
|
|
; CHECK-DAG: add {{x[0-9]+}}, sp, #{{[0-9]+}}
|
|
|
|
ret void
|
|
}
|