File: bank-conflict-load.mir

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 (28 lines) | stat: -rw-r--r-- 625 bytes parent folder | download | duplicates (7) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
 
# RUN: llc -march=hexagon -run-pass post-RA-sched %s -o - | FileCheck %s

# The two loads from %a ($r0) can cause a bank conflict. Check that they
# are not scheduled next to each other.

# CHECK: L2_loadri_io $r0, 8
# CHECK: L2_loadri_io killed $r1, 0
# CHECK: L2_loadri_io killed $r0, 12

--- |
  define void @foo(ptr %a, ptr %b) {
    ret void
  }
...

---
name: foo
tracksRegLiveness: true

body: |
  bb.0:
    liveins: $r0, $r1

    $r2 = L2_loadri_io $r0, 8 :: (load (s32) from %ir.a)
    $r3 = L2_loadri_io killed $r0, 12 :: (load (s32) from %ir.a)
    $r4 = L2_loadri_io killed $r1, 0 :: (load (s32) from %ir.b)
...