d391e4fe84
Be more consistent in the naming convention for the various RET instructions to specify in terms of bitwidth. Helps prevent future scheduler model mismatches like those that were only addressed in D44687. Differential Revision: https://reviews.llvm.org/D113302
27 lines
528 B
YAML
27 lines
528 B
YAML
# RUN: not llc -march=x86-64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
# This test ensures that an error is reported when an invalid global value index
|
|
# is used.
|
|
|
|
--- |
|
|
|
|
@0 = external global i32
|
|
|
|
define i32 @inc() {
|
|
entry:
|
|
%a = load i32, i32* @0
|
|
%b = add i32 %a, 1
|
|
ret i32 %b
|
|
}
|
|
|
|
...
|
|
---
|
|
name: inc
|
|
body: |
|
|
bb.0.entry:
|
|
; CHECK: [[@LINE+1]]:32: use of undefined global value '@2'
|
|
$rax = MOV64rm $rip, 1, _, @2, _
|
|
$eax = MOV32rm $rax, 1, _, 0, _
|
|
$eax = INC32r $eax
|
|
RET64 $eax
|
|
...
|