File: writing-to-stdout.ll

package info (click to toggle)
llvm-toolchain-13 1%3A13.0.1-11
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,418,840 kB
  • sloc: cpp: 5,290,826; ansic: 996,570; asm: 544,593; python: 188,212; objc: 72,027; lisp: 30,291; f90: 25,395; sh: 24,898; javascript: 9,780; pascal: 9,398; perl: 7,484; ml: 5,432; awk: 3,523; makefile: 2,913; xml: 953; cs: 573; fortran: 539
file content (16 lines) | stat: -rw-r--r-- 670 bytes parent folder | download | duplicates (29) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 
; REQUIRES: default_triple

; Often LLVM tools use "-" to indicate that output should be written to stdout
; instead of a file. This behaviour is implemented by the raw_fd_ostream class.
; This test verifies that when doing so multiple times we don't try to access a
; closed STDOUT_FILENO. The exact options used in this test are unimportant, as
; long as they write to stdout using raw_fd_ostream.
; RUN: llc %s -o=- -pass-remarks-output=- -filetype=asm | FileCheck %s
; foobar should appear as a function somewhere in the assembly file.
; CHECK: foobar
; !Analysis appears at the start of pass-remarks-output.
; CHECK: !Analysis

define void @foobar() {
  ret void
}