File: regbankselect-reg_sequence.mir

package info (click to toggle)

llvm-toolchain-11 1%3A11.0.1-2

links: PTS, VCS
area: main
in suites: bullseye
size: 995,808 kB
sloc: cpp: 4,767,656; ansic: 760,916; asm: 477,436; python: 170,940; objc: 69,804; lisp: 29,914; sh: 23,855; f90: 18,173; pascal: 7,551; perl: 7,471; ml: 5,603; awk: 3,489; makefile: 2,573; xml: 915; cs: 573; fortran: 503; javascript: 452

file content (22 lines) | stat: -rw-r--r-- 611 bytes

parent folder | download | duplicates (24)

# 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

...