File: target-flag-ext.mir

package info (click to toggle)
llvm-toolchain-20 1%3A20.1.6-1~exp1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 2,111,304 kB
  • sloc: cpp: 7,438,677; ansic: 1,393,822; asm: 1,012,926; python: 241,650; f90: 86,635; objc: 75,479; lisp: 42,144; pascal: 17,286; sh: 10,027; ml: 5,082; perl: 4,730; awk: 3,523; makefile: 3,349; javascript: 2,251; xml: 892; fortran: 672
file content (24 lines) | stat: -rw-r--r-- 833 bytes parent folder | download | duplicates (6) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
 
# RUN: llc -mtriple=hexagon -run-pass hexagon-packetizer -o - %s | FileCheck %s
---
name: fred
tracksRegLiveness: true

body: |
  bb.0:
    ; Check that all these instructions go in the same packet. This is to
    ; make sure that a target flag (other than HMOTF_ConstExtend) on an
    ; operand will not be interpreted as a constant-extender flag.
    ; The combination used below (pcrel + 0) does not technically make sense,
    ; but combinations that do make sense require constant extending, so
    ; testing this is not possible otherwise.

    ; CHECK: BUNDLE
    ; CHECK-DAG: $r0 = A2_tfrsi
    ; CHECK-DAG: $r1 = A2_tfrsi
    ; CHECK-DAG: $r2 = A2_tfrsi
    ; CHECK: }
    $r0 = A2_tfrsi target-flags (hexagon-pcrel) 0
    $r1 = A2_tfrsi target-flags (hexagon-pcrel) 0
    $r2 = A2_tfrsi target-flags (hexagon-pcrel) 0
...