Files
clang-p2996/llvm/test/CodeGen/MIR/X86/stack-object-operands.mir
Justin Lebar c75d566f56 When printing MIR, output to errs() rather than outs().
Summary:
Without this, this command

  $ llvm-run llc -stop-after machine-cp -o - <( echo '' )

outputs an error, because we close stdout twice -- once when closing the
file opened for "-o", and again when closing outs().

Also clarify in the outs() definition that you can't ever call it if you
want to open your own raw_fd_ostream on stdout.

Reviewers: jroelofs, tstellarAMD

Subscribers: jholewinski, qcolombet, dsanders, llvm-commits

Differential Revision: http://reviews.llvm.org/D17422

llvm-svn: 261286
2016-02-19 00:18:46 +00:00

46 lines
1.1 KiB
YAML

# RUN: llc -march=x86 -start-after machine-sink -stop-after machine-sink -o /dev/null %s 2>&1 | FileCheck %s
# This test ensures that the MIR parser parses stack object machine operands
# correctly.
--- |
define i32 @test(i32 %a) {
entry:
%b = alloca i32
%0 = alloca i32
store i32 %a, i32* %b
store i32 2, i32* %0
%c = load i32, i32* %b
ret i32 %c
}
...
---
name: test
isSSA: true
tracksRegLiveness: true
registers:
- { id: 0, class: gr32 }
- { id: 1, class: gr32 }
frameInfo:
maxAlignment: 4
fixedStack:
- { id: 0, offset: 0, size: 4, isImmutable: true, isAliased: false }
stack:
- { id: 0, name: b, size: 4, alignment: 4 }
- { id: 1, size: 4, alignment: 4 }
body: |
; CHECK: bb.0.entry:
; CHECK-NEXT: %0 = MOV32rm %fixed-stack.0, 1, _, 0, _
; CHECK-NEXT: MOV32mr %stack.0.b, 1, _, 0, _, %0
; CHECK-NEXT: MOV32mi %stack.1, 1, _, 0, _, 2
; CHECK-NEXT: %1 = MOV32rm %stack.0.b, 1, _, 0, _
bb.0.entry:
%0 = MOV32rm %fixed-stack.0, 1, _, 0, _
MOV32mr %stack.0.b, 1, _, 0, _, %0
MOV32mi %stack.1, 1, _, 0, _, 2
%1 = MOV32rm %stack.0, 1, _, 0, _
%eax = COPY %1
RETL %eax
...