mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2025-02-01 05:01:59 +01:00
95df870e77
llvm.frameescape() intrinsic is not a real call. The intrinsic can only exist in the entry block. Inserting a gc.statepoint() before llvm.frameescape() may split the entry block, and push the intrinsic out of the entry block. Patch by: Swaroop.Sridhar@microsoft.com Differential Revision: http://reviews.llvm.org/D8910 llvm-svn: 235820
30 lines
749 B
LLVM
30 lines
749 B
LLVM
; RUN: opt %s -S -place-safepoints | FileCheck %s
|
|
|
|
declare void @llvm.frameescape(...)
|
|
|
|
; Do we insert the entry safepoint after the frameescape intrinsic?
|
|
define void @parent() gc "statepoint-example" {
|
|
; CHECK-LABEL: @parent
|
|
entry:
|
|
; CHECK-LABEL: entry
|
|
; CHECK-NEXT: alloca
|
|
; CHECK-NEXT: frameescape
|
|
; CHECK-NEXT: statepoint
|
|
%ptr = alloca i32
|
|
call void (...) @llvm.frameescape(i32* %ptr)
|
|
ret void
|
|
}
|
|
|
|
; This function is inlined when inserting a poll. To avoid recursive
|
|
; issues, make sure we don't place safepoints in it.
|
|
declare void @do_safepoint()
|
|
define void @gc.safepoint_poll() {
|
|
; CHECK-LABEL: gc.safepoint_poll
|
|
; CHECK-LABEL: entry
|
|
; CHECK-NEXT: do_safepoint
|
|
; CHECK-NEXT: ret void
|
|
entry:
|
|
call void @do_safepoint()
|
|
ret void
|
|
}
|