File: arm64-separator.s

package info (click to toggle)
llvm-toolchain-16 1%3A16.0.6-15~deb11u2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 1,634,820 kB
  • sloc: cpp: 6,179,261; ansic: 1,216,205; asm: 741,319; python: 196,614; objc: 75,325; f90: 49,640; lisp: 32,396; pascal: 12,286; sh: 9,394; perl: 7,442; ml: 5,494; awk: 3,523; makefile: 2,723; javascript: 1,206; xml: 886; fortran: 581; cs: 573
file content (20 lines) | stat: -rw-r--r-- 694 bytes parent folder | download | duplicates (39) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
 
; RUN: llvm-mc -triple arm64-apple-darwin -show-encoding < %s | FileCheck %s

; ARM64 uses a multi-character statement separator, "%%". Check that we lex
; 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