Dear All, I downloaded the latest CVS of llvm I want to try to use LLVM only for JIT only use (generating code in memory for x86 and, when available PowerPC [32bits]) How do I ./configure to avoid being asked about llvmgcc, which, in my very partial understanding, is only used to parse C code... If I understand correctly what Chris Lattner emailed me, LLVM uses only GCC frontend for C & C++ parsing. I don't want to parse C or C++. I would just want to build the necessary libraries to compile and run llvm/examples/HowToUseJIT/HowToUseJIT.cpp and other similar examples. I want to use LLVM directly from its C++ API to build the "bytecode" tree (actually the sequence or tree of LLVM instructions), so I really don't need any C or C++ parser. (FWIW, I did know and use GNU lightning) Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net aliases: basile<at>tunes<dot>org = bstarynk<at>nerim<dot>net 8, rue de la Faïencerie, 92340 Bourg La Reine, France
On Sun, Nov 07, 2004 at 10:33:09PM +0100, Basile STARYNKEVITCH wrote:> I want to try to use LLVM only for JIT only use (generating code in > memory for x86 and, when available PowerPC [32bits])Cool! FYI, the PowerPC JIT needs work to make it operational, but the x86 JIT is good to go.> How do I ./configure to avoid being asked about llvmgcc, which, in my > very partial understanding, is only used to parse C code... If I > understand correctly what Chris Lattner emailed me, LLVM uses only GCC > frontend for C & C++ parsing. I don't want to parse C or C++.Don't worry about the configure errors at the end, and just run "make tools-only". That will build all the libraries and LLVM tools, but not build the runtime libraries (which require llvm-gcc).> I would just want to build the necessary libraries to compile and run > llvm/examples/HowToUseJIT/HowToUseJIT.cpp and other similar examples.They will be built automatically at the end of the build. If you really don't want to link any of the tools, comment them out in tools/Makefile (set PARALLEL_DIRS to nothing). You can't just go into llvm/lib and run 'make' because some of the libraries need to have utilities built first (llvm/utils) which, in turn, need some basic libraries (Support and System).> I want to use LLVM directly from its C++ API to build the "bytecode" > tree (actually the sequence or tree of LLVM instructions), so I really > don't need any C or C++ parser.Makes sense. HTH, -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu
Hello List, (apparently this list is moderated) Le/On Sun, Nov 07, 2004 at 03:45:41PM -0600, Misha Brukman écrivait/wrote:> On Sun, Nov 07, 2004 at 10:33:09PM +0100, Basile STARYNKEVITCH > wrote:Basile>> I want to try to use LLVM only for JIT only use (generating code in Basile>> memory for x86 and, when available PowerPC [32bits]) If you want to know I am experimenting some JIT generation for a experimental toy functional language [this is only a hobby] and I did write the OcamlJIT (a JIT translator of Ocaml bytecode using GNU lightning)> Cool! FYI, the PowerPC JIT needs work to make it operational, but the > x86 JIT is good to go.> Don't worry about the configure errors at the end, and just run > "make tools-only". That will build all the libraries and LLVM tools, > but not build the runtime libraries (which require llvm-gcc).First, I am extremely confused by the terminology. IMHO, the runtime libraries would include (from my JIT only perspective) 1. all the LLVM libraries required to JIT-generate machine code, and to build a representation of the LLVM instruction sequence or tree. Z. the garbage collection I'm coding for my toy language. So I really can't figure why is the LVM-GCC parser needed here! For me the runtime stuff of LLVM is the stuff I need to JIT (without C parsing) - but I am wrong! what exactluy is the "runtime" and why does it require llvm-gcc (I thought that LLVM is not a bootstrapped language: the compiler is not written in LLVM...) Second trivial question: only I "make tools-only" how can I install the stuff (in the standard /usr/local/ prefix)? Does "sudo make install" is enough? Regards. -- Basile STARYNKEVITCH http://starynkevitch.net/Basile/ email: basile<at>starynkevitch<dot>net aliases: basile<at>tunes<dot>org = bstarynk<at>nerim<dot>net 8, rue de la Faïencerie, 92340 Bourg La Reine, France