similar to: [LLVMdev] Preservance of function variables in the bytecode

Hello, LLVM-Dev guys. I just wonder if function variables are preserved in the bytecode. For example, are i and j in the following function preserved in .bc? int sum(int i, int j){ int k; k = i + j; return k; } I tested this with "llc -march=c" and found this was converted to int sum(int ltmp_0_1, int ltmp_1_1) { return (ltmp_1_1 + ltmp_0_1); } Therefore, it seems

Hi, I want to get the mapping between C source's variables and bytecode variables. It seems that llvm doesn't provide this mapping, so I think a walk-around method is to get the instruction's mapping. I have to use llvm-gcc, not clang. Any advice? Thanks. Best, Kecheng 2010-05-13 From: Eli Friedman Date: 2010-05-13 15:38:36 To: Kecheng Cc: llvmdev Subject: Re: [LLVMdev] How

Eli, Thanks very much for your reply. That's what I want to know. It works for this example. But I usually have to deal with the optimized bytecode with "-O". See the example: ************** C source ************** int h (int j, int i) { int tmp; tmp = j+i+2; return tmp; } +++++++++++++++++++++++++++++++++++++ .ll file: ; ModuleID = 'simplecase.c' target

Hi, I want to know the variable mapping between the source and llvm bytecode. It seems that current llvm debugging information cannot provide this mapping directly. Here is my examples (llvm 2.7). In this exmaple, I want to know the mapping: tmp<--->%4. But current llvm's debugging information can only provide that the instruction "%4 = add nsw i32 %3, 2" is at line 3 in

Hello, guys. I just wonder if there is any way to spit out LLVM assembly without any basic block division. E.g., If I emit LLVM assembly for the following simple code: ------------------------------------------------------------ void f_loop(long* c, long sz) { long i; for (i = 0; i < sz; i++) { long offset = i * sz; long* out = c + offset; out[i] = 0; } }

Dear Wojciech Matyjewicz: Thank you for your advice. I could follow what you had suggested upto opt -analyze -loops bsloop-opt.bc Therefore, I could get the prints you had showed me as follows: -------------------------------------------------------- Printing analysis 'Natural Loop Construction' for function 'bsloop': Loop Containing: %bb16, %bb13, %bb8, %bb1 Loop

Wow... Thank you so much for this. I'll try this one. Thanks again, Wojciech. SJL ---- Original message ---- >Date: Sat, 15 Sep 2007 15:07:34 +0200 >From: Wojciech Matyjewicz <wmatyjewicz at fastmail.fm> >Subject: Re: [LLVMdev] constructing 'for' statement from LLVM bitcode >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >Hi, >

On Fri, 2006-11-24 at 21:13 +0100, Philipp Klaus Krause wrote: > Reid Spencer schrieb: > Hmm the problem was a bit different. I just reproduced it. > > I used this input file: > > #include <stdint.h> > > uint32_t test(uint32_t t) > { > return(t + 42); > } > > and got the following code: > > unsigned test(unsigned ltmp_0_1) { > return

Thank you for your kind explanation. I did it as you mentioned. That is, I set '-march=x86 hello.bc' in the Command Arguments. (I also set my compiled LLC, i.e., LLVM_ROOT_DIR\win32\debug\llc.exe, in the property name Command.) But, when I made a breakpoint in main( ) of llc.cpp and then started to debug I found the 'InputFilename'(llc.cpp:176) is shown like {???}. Therefore it

Hello. My name is Seung Jae Lee. I'd like to ask you onething about converting to ARM assembly code. I saved the simplest C code shown in your LLVM webpage as 'hello.c' And I made 'hello.bc' by "$ llvm-gcc hello.c -o hello". In order to make ARM assembly code, I typed "llc -march=arm hello.bc -o hello.arm" But, I met this error. llc: ARMISelDAGToDAG.cpp:73:

No, No... That's OK. I appreciate your concerns. Seung Jae Lee ---- Original message ---- >Date: Mon, 16 Apr 2007 13:30:59 -0700 >From: Jeff Cohen <jeffc at jolt-lang.org> >Subject: Re: [LLVMdev] adding a target for "-march=" option in Visual Studio (Resolved) >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >Seung Jae Lee wrote:

Thank you so much for your reply, Chris. If so, can I ask you two things more? First, is there any way to have various optimizations on LLVM assembly such as -O options in llvmc? llvm-gcc doesn't seem to be working for these -O options... Second, I'm still not sure about difference between *.s and *.ll. LLVM assembly *.s file can be made from llvm-gcc -S. Another assembly *.ll file comes

Reid Spencer schrieb: > Hi Philipp, > > On Fri, 2006-11-24 at 20:09 +0100, Philipp Klaus Krause wrote: >> Reid Spencer schrieb: >> >>> Note that C and LLVM types are *not* the same things (despite the >>> similar names). We are in the process of making this abundantly clear. >>> The LLVM IR will soon use names like i8, i16, i32, and i64 (signless

Bill, Depending on what Seung's problem is, converting *out* of SSA form may actually be the wrong thing to do. Seung needs to explain exactly problem he is unable solve using SSA form. --Vikram http://www.cs.uiuc.edu/~vadve http://llvm.org/ On Jan 28, 2008, at 1:10 AM, Bill Wendling wrote: > Hi Seung, > > It should be fairly straight-forward to do in LLVM. Once you

Hello. I am Seung Jae Lee making a LLVM backend for a new architecture XCC. I found that the instructions use variable names which actually used in the source coding for operands unlike most architectures which use usually register names or addresses as operands. LLVM backend examples such as ARM, SPARC seem to use register names or addresses for operands. How can I implement this on my backend?

Hi Seung, It should be fairly straight-forward to do in LLVM. Once you identify the loops, then identify the PHI nodes that you need to convert, then apply the transformation below. The fine details on how to create an instruction and replace one instruction with another are documented in the docs section and in other code. :-) One thing to be careful of, if you convert a variable like

Hello. Nice to meet you. My name is Seung Jae Lee, a graduate student in UIUC CEE, who is working in NCSA for the present. Nowadays I am trying to develop LLVM backend to spit out CHiMPS assembly code. In the process, I installed LLVM codes on my home directory in the host computer. But I don't think it was installed properly. While bootstrapping the LLVM C/C++ Front-End, I met several

Seung Jae Lee wrote: > I followed the steps in "Getting Started with the LLVM System using Microsoft Visual Studio" in the document in LLVM page. > > I made hello.c file exactly same shown in the page. > I made hello.bc on UNIX and transferred it to my Windows computer. > And I typed "llc -march=c hello.bc" > (Of course, I downloaded the latest version of LLVM

Thank you so much for your reply, Chris. If so, can I ask you two things more? First, is there any way to have various optimizations on LLVM assembly such as -O options in llvmc? llvm-gcc doesn't seem to be working for these -O options... Second, I'm still not sure about difference between *.s and *.ll. LLVM assembly *.s file can be made from llvm-gcc with -S option. Another

Thanks--I was offline when I wrote it, couldn't Google. Found it in about 5 seconds once I was back online. Second question: I'm getting various build errors relating (it seems) to configuration: can't find windows.h and so forth. Where (or to whom) is the best place to report these and iterate until we fix them? Ted Neward Java, .NET, XML Services Consulting, Teaching, Speaking,