[llvm-commits] [llvm] r46399 - /llvm/trunk/test/Transforms/Inline/byval2.ll

[Duncan Sands]

Author: baldrick
Date: Sat Jan 26 06:33:01 2008
New Revision: 46399

URL: http://llvm.org/viewvc/llvm-project?rev=46399&view=rev
Log:
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?).

Modified:
    llvm/trunk/test/Transforms/Inline/byval2.ll

Modified: llvm/trunk/test/Transforms/Inline/byval2.ll
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/test/Transforms/Inline/byval2.ll?rev=46399&r1=46398&r2=46399&view=diff

==============================================================================
--- llvm/trunk/test/Transforms/Inline/byval2.ll (original)
+++ llvm/trunk/test/Transforms/Inline/byval2.ll Sat Jan 26 06:33:01 2008
@@ -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]