reference, declarationdefinition
definition → references, declarations, derived classes, virtual overrides
reference to multiple definitions → definitions
unreferenced
    1
    2
    3
    4
    5
    6
    7
    8
    9
   10
   11
   12
   13
   14
   15
   16
   17
   18
   19
   20
   21
   22
   23
   24
   25
   26
   27
   28
   29
   30
; RUN: llc < %s -mcpu=generic -mtriple=i686-linux -verify-machineinstrs | FileCheck %s -check-prefix=X32-Linux
; RUN: llc < %s -mcpu=generic -mtriple=x86_64-linux  -verify-machineinstrs | FileCheck %s -check-prefix=X64-Linux

; 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 {
	ret void
}

attributes #0 = { "split-stack" }

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

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

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

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

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