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
19 lines
347 B
YAML
19 lines
347 B
YAML
# RUN: not llc -march=x86-64 -run-pass none -o /dev/null %s 2>&1 | FileCheck %s
|
|
|
|
--- |
|
|
|
|
define i32 @foo() {
|
|
entry:
|
|
ret i32 42
|
|
}
|
|
|
|
...
|
|
---
|
|
name: foo
|
|
body: |
|
|
bb.0.entry:
|
|
; CHECK: [[@LINE+1]]:20: integer literal is too large to be an immediate operand
|
|
$eax = MOV32ri 12346127502983478823754212949184914
|
|
RET64 $eax
|
|
...
|