File: global-get-unlowerable.ll

package info (click to toggle)
llvm-toolchain-21 1%3A21.1.1-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 2,236,080 kB
  • sloc: cpp: 7,618,171; ansic: 1,433,906; asm: 1,058,726; python: 252,113; f90: 94,671; objc: 70,753; lisp: 42,813; pascal: 18,401; sh: 10,069; ml: 5,111; perl: 4,720; awk: 3,523; makefile: 3,397; javascript: 2,272; xml: 892; fortran: 770
file content (17 lines) | stat: -rw-r--r-- 641 bytes parent folder | download | duplicates (15)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
; RUN: not llc < %s --mtriple=wasm32 2>&1 | FileCheck %s

; Demonstrates a code pattern that could be encountered even with frontend
; restrictions on creating new pointers to globals. In the absence of a better
; fix, the backend should produce a comprehensible message for why it can't
; continue.

; CHECK: LVM ERROR: Encountered an unlowerable load from the wasm_var address space

@g1 = external addrspace(1) global i32
@g2 = external addrspace(1) global i32

define i32 @global_get_phi(i1 zeroext %bool) {
  %sel = select i1 %bool, ptr addrspace(1) @g1, ptr addrspace(1) @g2
  %gval = load i32, ptr addrspace(1) %sel
  ret i32 %gval
}