Invert this test, because it is wrong if we allow

readonly functions to use byval parameters as local
storage (how much do we want this?).


git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@46399 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Duncan Sands 2008-01-26 12:33:01 +00:00
parent 824a721560
commit 63b2c2dde7

View File

@ -1,7 +1,7 @@
; RUN: llvm-as < %s | opt -inline | llvm-dis | not grep {llvm.memcpy}
; RUN: llvm-as < %s | opt -inline | llvm-dis | grep {llvm.memcpy}
; Inlining a byval struct should NOT cause an explicit copy
; into an alloca if the function is readonly
; Inlining a byval struct should cause an explicit copy
; into an alloca even if the function is readonly
%struct.ss = type { i32, i64 }
@.str = internal constant [10 x i8] c"%d, %lld\0A\00" ; <[10 x i8]*> [#uses=1]