diff options
Diffstat (limited to 'test/Transforms/Inline')
| -rw-r--r-- | test/Transforms/Inline/byval-tail-call.ll (renamed from test/Transforms/Inline/2010-05-31-ByvalTailcall.ll) | 21 |
1 files changed, 17 insertions, 4 deletions
diff --git a/test/Transforms/Inline/2010-05-31-ByvalTailcall.ll b/test/Transforms/Inline/byval-tail-call.ll index 07ea5fc6cc..3a8906aa21 100644 --- a/test/Transforms/Inline/2010-05-31-ByvalTailcall.ll +++ b/test/Transforms/Inline/byval-tail-call.ll @@ -1,10 +1,8 @@ ; RUN: opt < %s -tailcallelim -inline -instcombine -dse -S | FileCheck %s ; PR7272 -; When inlining through a byval call site, the inliner creates allocas which may -; be used by inlined calls, so any inlined calls need to have their 'tail' flags -; cleared. If not then you can get nastiness like with this testcase, where the -; (inlined) call to 'ext' in 'foo' was being passed an uninitialized value. +; Calls that capture byval parameters cannot be marked as tail calls. Other +; tails that don't capture byval parameters can still be tail calls. target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32-n8:16:32" target triple = "i386-pc-linux-gnu" @@ -23,3 +21,18 @@ define void @foo(i32* %x) { call void @bar(i32* byval %x) ret void } + +define internal void @qux(i32* byval %x) { + call void @ext(i32* %x) + tail call void @ext(i32* null) + ret void +} +define void @frob(i32* %x) { +; CHECK-LABEL: define void @frob( +; CHECK: alloca i32 +; CHECK: {{^ *}}call void @ext( +; CHECK: tail call void @ext(i32* null) +; CHECK: ret void + tail call void @qux(i32* byval %x) + ret void +} |