similar to: [LLVMdev] Backend to start with

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:

Xi, I just installed VS2005 pro w/ SP1 for Win Vista. Thanks, Seung ---- Original message ---- >Date: Fri, 22 Feb 2008 12:36:43 +0800 >From: "Xi Wang" <xi.wang at gmail.com> >Subject: Re: [LLVMdev] Is there someone tried LLVM 2.1 on Visual Studio 2005? >To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> > >I'm sorry but did you

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?

Dear Mr. Cheng: Thank you for kind information. Can you tell me in more detail about that? For example, I am trying to implement 'demultiplex' instruction as follows: demultiplex <multiplexid,choose,branch0id,branch1id,…,otherwisebranchid> In this case, the number of branch#id is not definite. It can be 1, 2, 3...or any number. My question was about this. I am still not sure how

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

Ok, here are a few suggestions and comments: 1) LLVM has the capabilities to do everything that you are trying to re-implement. 2) Have you looked at the C backend? It recreates loops. It may not create "for" loops but you can hack on it to do that. 3) The way you are converting out of SSA is wrong. You will suffer from lost copies. You should look at using demotePHI(). see

try here: http://sourceforge.net/projects/inger this project have a ebook (Compiler Construction: A Practical Approach) that covers some backend code generation techniques. On 2/1/07, Seung Jae Lee <lee225 at uiuc.edu> wrote: > Can you recommend any good book or reference for backend implementation? I skimmed some compiler books but it seemed to be more about front-end, parsing,

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

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

Thank you, Patrick. What I want to do is just to write those source level variable names in my assembly code for a virtual machine because it is instructed in its instructions manual. I registered the VM as a target for LLC and want to emit the assembly. For this reason, I asked how to get the variables themselves which are not mangled from the bytecode. Thanks to your help, now I see they can be

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

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

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

Thank you for this reply. However, I've already read this thesis. (Mr. Doug Simon in Sun microsystems I mentioned was her student.) This is a quite good article for reverse engineering but this is only useful for my alternative way which is trying to derive HL code from a machine assembly. This thesis is a little bit old before SSA form becomes quite popular so does not deal with any PHI

On 19/07/2007 01:29:18, Seung Jae Lee (lee225 at uiuc.edu) wrote: > Somebody in this dev-list alreday did it with LLVM. I guess you are speaking about Bruno Cardoso Lopes ? I can see there is a MIPS implementation in LLVM repository but it looks like uncomplete (that is, I'm not even sure it can compile any source). What I hope is to have a complete MIPS implementation so I can adapt

Thank you so much for this info. That's exactly what I want. But, I'm still not sure about using -g. Let me imagine I am modifying x86 assembly instructions and trying to test it with 'hello.c' to check out the assembly is properly emitted. I should type "$ llvm-gcc hello.c -o hello" to have the bytecode of 'hello.c'. And then I can have an x86 assembly mnemonics

Thank you for this information. If so, is there any way to grasp which kinda data throw in and out in LLVM as shown in such a way in gdb? Thanks, Seung Jae Lee ---- Original message ---- >Date: Tue, 20 Feb 2007 23:54:04 -0600 >From: "John T. Criswell" <criswell at cs.uiuc.edu> >Subject: Re: [LLVMdev] bugpoint usage >To: LLVM Developers Mailing List <llvmdev at

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,