On Aug 14, 2007, at 12:25 PM, Reid Spencer wrote: > Chris > > On Tue, 2007-08-14 at 16:19 +0000, Chris Lattner wrote: >> Author: lattner >> Date: Tue Aug 14 11:19:35 2007 >> New Revision: 41073 >> >> URL: http://llvm.org/viewvc/llvm-project?rev=41073&view=rev >> Log: >> tcl seems to hate |& for some reason. >> >> Modified: >> llvm/trunk/test/CodeGen/X86/constant-pool-remat-0.ll >> >> Modified: llvm/trunk/test/CodeGen/X86/constant-pool-remat-0.ll >> URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/test/CodeGen/ >> X86/constant-pool-remat-0.ll?rev=41073&r1=41072&r2=41073&view=diff >> >> ===================================================================== >> ========= >> --- llvm/trunk/test/CodeGen/X86/constant-pool-remat-0.ll (original) >> +++ llvm/trunk/test/CodeGen/X86/constant-pool-remat-0.ll Tue Aug >> 14 11:19:35 2007 >> @@ -1,6 +1,6 @@ >> ; RUN: llvm-as < %s | llc -march=x86-64 | grep LCPI | count 3 >> ; RUN: llvm-as < %s | llc -march=x86 -mattr=+sse2 | grep LCPI | >> count 3 >> -; RUN: llvm-as < %s | llc -march=x86 -mattr=+sse2 -stats |& | >> grep asm-printer | grep 13 > > |& works fine (see test/Feature/load_module.ll). The problem is the > double pipe. |& | is not legal (no command in the pipeline). |& means > send both stdin and stderr through the pipe, not just stderr.
Actually no it doesn't. I tried just |& and it didn't detect the failure. -Chris _______________________________________________ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
