similar to: [LLVMdev] Registering '-march=' option for LLC

On Fri, 17 Nov 2006, Seung Jae Lee wrote: > Thank you for replying to me. As you recommended, I modified > configure.ac in autoconf folder. But I’m not sure about how to > regenerate configure. Sorry… > I tried to follow the way introduced in README.TXT in the autoconf > folder. It asks me to run autoupdate on all the m4 and configure.ac. And > then it asks me to regenerate

On Fri, 2006-11-17 at 17:19 -0800, Tanya M. Lattner wrote: > On Fri, 17 Nov 2006, Seung Jae Lee wrote: > > > Thank you for replying to me. As you recommended, I modified > > configure.ac in autoconf folder. But I’m not sure about how to > > regenerate configure. Sorry… > > I tried to follow the way introduced in README.TXT in the autoconf > > folder. It asks

Hello. I am making a LLVM backend for a new architecture XCC. During implementation of instructions for XCC, I found that there are instructions need more than 3 operands in the target language manual. I could implement insructions need 1, 2 or 3 operands thanks to the examples in the LLVM backends already offered by you guys. But, I am not sure about those kind of instructions needs many number

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?

I resolved this by adding the path of .obj file in the linker options in LLC property page. Thank you. Seung Jae Lee

On 2/23/07, Reid Spencer <rspencer at reidspencer.com> wrote: > > However, if I run the AutoRegen.sh script (after modifying it to > > accept autoconf 2.61, which I think is fine as gentoo slots it the > > same as the 2.5[0-9] versions), the configure no longer works: > > ~/programming/llvm-1.9/projects/zhe $ cd autoconf/ > >

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:

Thank you for reminding me the notion of the basic block. Of course, I know all the assembly takes the form of BBs and is divided into units of BB. OK. It looks better for me to explain what I wanted to do more clear from the first. Actually, I am working on emitting out an assembly of VM by using LLVM. LLVM assembly looks similar with this VM assembly except BB. The VM assembly does not have the

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, Bill. Seems to be better. Anyway...Is there a way I can do what you showed for me? Thanks, Seung J. Lee ---- Original message ---- >Date: Sat, 26 Jan 2008 22:10:01 -0800 >From: Bill Wendling <isanbard at gmail.com> >Subject: Re: [LLVMdev] Question to Chris >To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > >On Jan 26, 2008, at 9:48 AM, Seung

Thanks for your comment. I also tried for LLVM 2.2 but got the same compilation errors on VS2005. (I didn't modify anything before the compilation) I just wonder if I need bison and flex even just in the case of compiling them on VS2005 without changing anything because the LLVM doc says "If you plan to modify any .y or .l files, you will need to have bison and/or flex installed where

Hello. I am trying to run tblgen so I typed $ tblgen ARM.td -print-enums -class=Register in "llvm/lib/Target/ARM" But I got an error as follows: Included from ARM.td:18: Parsing ../Target.td:16: Could not find include file 'llvm/Intrinsics.td'! As you know, the 16th line of Target.td includes "llvm/Intrinsics.td". But this cannot find Intrinsics.td, I think. Of

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

I have always built it with flex and bison installed, though I believe Chris removed our last dependence on flex a little while back, so you may not need that. I'm using bison 2.1 which I got from the getgnuwin32 folks. I imagine that if you have cygwin or the like, you probably already have everything. You will need to have the executables in your path. I build with VisualStudio 2k5

Hello, LLVMers. I just wonder How I can pronounce Clang. [see-laeng], [see-lang], [k-laeng], [k-lang]?? Thanks, Seung

I simply found it at: http://getgnuwin32.sourceforge.net/ Seung ---- Original message ---- >Date: Tue, 12 Feb 2008 21:11:04 -0800 >From: "Ted Neward" <ted at tedneward.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,

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

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

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 and compiled with VS before this.) But my command