maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/llvm/test/MC/AArch64/arm64-separator.s

21 lines
694 B
ArmAsm
Raw Normal View History

ARM64: initial backend import This adds a second implementation of the AArch64 architecture to LLVM, accessible in parallel via the "arm64" triple. The plan over the coming weeks & months is to merge the two into a single backend, during which time thorough code review should naturally occur. Everything will be easier with the target in-tree though, hence this commit. llvm-svn: 205090
2014-03-29 18:18:08 +08:00
; RUN: llvm-mc -triple arm64-apple-darwin -show-encoding < %s | FileCheck %s
Fix some doc and comment typos llvm-svn: 205899
2014-04-09 22:47:27 +08:00
; ARM64 uses a multi-character statement separator, "%%". Check that we lex
ARM64: initial backend import This adds a second implementation of the AArch64 architecture to LLVM, accessible in parallel via the "arm64" triple. The plan over the coming weeks & months is to merge the two into a single backend, during which time thorough code review should naturally occur. Everything will be easier with the target in-tree though, hence this commit. llvm-svn: 205090
2014-03-29 18:18:08 +08:00
; it properly and recognize the multiple assembly statements on the line.
; To make sure the output assembly correctly handled the instructions,
; tell it to show encodings. That will result in the two 'mov' instructions
; being on separate lines in the output. We look for the "; encoding" string
; to verify that. For this test, we don't care what the encoding is, just that
; there is one for each 'mov' instruction.
_foo:
; CHECK: foo
; CHECK: mov x0, x1 ; encoding
; CHECK: mov x1, x0 ; encoding
mov x0, x1 %% mov x1, x0
ret lr