search for: zhiruz

...assManager::runOnFunction(llvm::Function&)+0xff)[0x85ce667] opt(llvm::MPPassManager::getOnTheFlyPass(llvm::Pass*, llvm::PassInfo const*, llvm::Function&)+0x62)[0x85ce85e] opt(llvm::AnalysisResolver::findImplPass(llvm::Pass*, llvm::PassInfo const*, llvm::Function&)+0x33)[0x85cbc39] /home/zhiruz/AutoESL/AutoPilot/trunk/build/obj-Linux-x86-g++/Debug/lib/libLLVMHello.so(llvm::LoopInfo& llvm::Pass::getAnalysisID<llvm::LoopInfo>(llvm::PassInfo const*, llvm::Function&)+0x99)[0x12efc7] /home/zhiruz/AutoESL/AutoPilot/trunk/build/obj-Linux-x86-g++/Debug/lib/libLLVMHello.so(llvm::Loop...

...change of the information, we also want on-disk exchange. That introduces the write-out/parse-in problem. Thanks ----- Original Message ----- From: "Misha Brukman" <brukman at uiuc.edu> To: "Yiping Fan" <fanyp at CS.UCLA.EDU>; "'Zhiru Zhang'" <zhiruz at CS.UCLA.EDU>; "Guoling Han" <leohgl at CS.UCLA.EDU> Cc: <llvmdev at cs.uiuc.edu> Sent: Wednesday, October 20, 2004 11:43 AM Subject: Re: LLVM Compiler Infrastructure Tutorial > I'm CC'ing the llvm-dev list because other people are more knowledgeable > ab...

I'm CC'ing the llvm-dev list because other people are more knowledgeable about the bytecode format/encoding than I am. Please follow-up the replies to the list. On Wed, Oct 20, 2004 at 11:27:53AM -0700, Yiping Fan wrote: > We also want to extend the llvm instructions/intrinsic > functions/types/passes to support our high-level synthesis for > hardware. First of all, we want to

...edu> ----- Date: Mon, 31 Oct 2005 17:20:24 -0800 From: "Yiping Fan" <fanyp at cs.ucla.edu> To: "Misha Brukman" <brukman at uiuc.edu>, "guoling han" <leohgl at cs.ucla.edu>, <cong at cs.ucla.edu>, "'Zhiru Zhang'" <zhiruz at cs.ucla.edu> Cc: "Brian Gaeke" <gaeke at uiuc.edu> Subject: Re: LLVM Compiler Infrastructure Hi Misha, How are you doing recently? It has been long time since the last email we exchanged. We used your LLVM compiler in our xPilot behavioral synthesis system, and made grea...

Hi, I am trying to turn on the new GCC auto-vectorization feature within llvmgcc4. Below is the command I used, but nothing was vectorized. Does it mean that llvmgcc4 has disabled this optimization and all I can do is to embed SSE intrinsics in the source code by hand? Thanks! ./llvm-gcc4-x86/bin/llvm-gcc -c -O2 -ftree-vectorize -msse -ftree-vectorizer-verbose=5 -emit-llvm vec.c -o vec.bc