File: bank-conflict-load.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 (28 lines) | stat: -rw-r--r-- 615 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(i32* %a, i32* %b) {
    ret void
  }
...

---
name: foo
tracksRegLiveness: true

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

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