File: segmented-stacks-standalone.ll

package info (click to toggle)
llvm-toolchain-20 1%3A20.1.6-1~exp1
  • links: PTS, VCS
  • area: main
  • in suites: experimental
  • size: 2,111,304 kB
  • sloc: cpp: 7,438,677; ansic: 1,393,822; asm: 1,012,926; python: 241,650; f90: 86,635; objc: 75,479; lisp: 42,144; pascal: 17,286; sh: 10,027; ml: 5,082; perl: 4,730; awk: 3,523; makefile: 3,349; javascript: 2,251; xml: 892; fortran: 672
file content (22 lines) | stat: -rw-r--r-- 911 bytes parent folder | download | duplicates (18) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
; RUN: llc < %s -mcpu=generic -mtriple=i686-linux -verify-machineinstrs | FileCheck %s
; RUN: llc < %s -mcpu=generic -mtriple=x86_64-linux  -verify-machineinstrs | FileCheck %s

; This test is standalone because segmented-stacks.ll generates
; object-files with both .note.GNU-split-stack (for the split-stack
; functions) and .note.GNU-no-split-stack sections (for the
; non-split-stack functions). But a split-stack function without a
; stack frame should have a .note.GNU-split-stack section regardless
; of any other contents of the compilation unit.

define void @test_nostack() #0 {
; CHECK-LABEL: test_nostack:
; CHECK:       # %bb.0:
; CHECK-NEXT:    ret{{[l|q]}}
	ret void
}

attributes #0 = { "split-stack" }

; CHECK: .section ".note.GNU-split-stack","",@progbits
; CHECK: .section ".note.GNU-no-split-stack","",@progbits