File: regbankselect-reg_sequence.mir

package info (click to toggle)
llvm-toolchain-19 1%3A19.1.7-10.1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,999,140 kB
  • sloc: cpp: 6,951,711; ansic: 1,486,157; asm: 913,598; python: 232,024; f90: 80,126; objc: 75,281; lisp: 37,276; pascal: 16,990; sh: 10,033; ml: 5,058; perl: 4,724; awk: 3,523; makefile: 3,252; javascript: 2,504; xml: 892; fortran: 664; cs: 573
file content (22 lines) | stat: -rw-r--r-- 611 bytes parent folder | download | duplicates (30) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
# RUN: llc %s -mtriple aarch64-- -o - -run-pass regbankselect | FileCheck %s
---
# CHECK-LABEL: foo
# Check that we produce a valid mapping for REG_SEQUENCE.
# This used to fail the RegisterBankInfo verify because
# we were using the exclusively the type of the definition
# whereas since REG_SEQUENCE are kind of target opcode
# their definition may not have a type.
#

# CHECK: %0:fpr(s128) = REG_SEQUENCE $d0, %subreg.dsub0, $d1, %subreg.dsub1

name: foo
legalized: true
tracksRegLiveness: true
body: |
  bb.0:
    liveins: $d0, $d1

    %0:_(s128) = REG_SEQUENCE $d0, %subreg.dsub0, $d1, %subreg.dsub1

...