search for: fanyp

...the answer to your question, but I am forwarding it to the LLVMdev list where I am sure someone will be able to answer you. Please send development questions directly to LLVMdev and you will get a response quicker, as it is read by many LLVM developers. ----- Forwarded message from Yiping Fan <fanyp at cs.ucla.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'...

...cute on a certain functional unit, etc. Besides the in-memory exchange 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...

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

During my project, it was very slow when I linked my program with the static libraries vmcore, asmparser, and support.a. Then I tried to compile these LLVM modules as shared libraries, by set SHARED_LIBRARY = 1 for those makefiles. It did generate the *.so libraries. However, when I linked with the shared libraries, it always complained that ...llvm/lib/Debug/libsupport.so: undefined reference

When I tried LLVM for a function with an array as an argument, the type infomation of the array seems lost. For example, for this function, void DCT(short data[64], char step, char offset), its corresponding LLVM code will be void %DCT8_int(short* %data, sbyte %step, sbyte %offset) , and every access of "data" will be a pointer access, instead of an array access. Is there any way to

> > ------------------------------ > > Message: 3 > Date: Tue, 18 Oct 2005 15:20:29 -0500 > From: "Robert L. Bocchino Jr." <bocchino at uiuc.edu> > Subject: [LLVMdev] Vector LLVM checked in! > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Message-ID: <64dde68b5934d83056aeb3c9f66afe7e at uiuc.edu> > Content-Type: text/plain;

Problem 1: I tried llvm-db of LLVM 1.6, in the Linux environment. However, it always prompts the following info for different tests: ====================================== :> llvm-db a.out.bc llvm-db: The LLVM source-level debugger Loading program... successfully loaded 'a.out.bc'! (llvm-db) run Starting program: a.out.bc Error: Error waiting for the child process to stop. It exited

Chris, thank you for your reply. Our problem is that we don't assume an integer must have 32 bits. In our code generation, we can define an integer to be less than 32 bits. For example, 24 bits. In this case, by executing this LLVM code (my first example) on a 24-bit machine, let x = 0xFFFFFF, then we will get %tmp.2 = 0x003FFF, and %tmp.3 = 0x3FFF, which is positive. That is not correct

Vikram, I also agree with you. I understand that target-independent representation is very valuable and important for software compilation. However, when we are doing high-level synthesis (also called behavioral/architectural synthesis), the targeting architecture is also changing. That is, we need to do architecture exploration and the IR transfromation simultaneously. For example,