similar to: [LLVMdev] Getting Started with LLVM

> 1) The only supported way to link against LLVM from outside the build > directory is to use Makefile.common and the LLVM build system, both of > which require an LLVM build tree. Without extensive customization: > a) I can't link against the installed LLVM libraries and headers. > b) I can't use my projects' pre-existing build systems (automake, > rake, or

On Mar 10, 2006, at 2:57 PM, Martin Pärtel wrote: > I'm currently using the "make install"-ed version of LLVM in an > autoconf/automake project. Setting it up wasn't that bad really. > The .a > libraries can be statically linked with the -l flag and .o > libraries are > simply linked in as normal object files (without -l). All the > libraries got >

One thing that helps me understand complex software is a dependency graph. I found an LLVM dependency graph at https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies but it's really messy and hard to follow. From that graph I made a cleaner graph by hand (attached)... sorry about the fax-quality scan. But I have some questions about it... -

Hi I'm trying to compile HowToUseJIT.cpp, but it seems that iterator definition is missing: --------------------Configuration: HowToUseJIT - Win32 Debug-------------------- Compiling... HowToUseJIT.cpp c:\sfu\usr\local\src\llvm\include\llvm\adt\ilist(41) : fatal error C1083: Cannot open include file: 'llvm/ADT/iterator': No such file or directory Error executing cl.exe. I've

David Piepgrass <dpiepgrass at mentoreng.com> writes: > One thing that helps me understand complex software is a dependency > graph. I found an LLVM dependency graph at > > https://llvm.org/svn/llvm-project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies > > but it's really messy and hard to follow. From that graph I made a > cleaner graph by hand

> > I found an LLVM dependency graph at > > > > https://llvm.org/svn/llvm- > project/llvm/tags/RELEASE_16/docs/UsingLibraries.html#dependencies > > > > but it's really messy and hard to follow. From that graph I made a > > cleaner graph by hand (attached)... sorry about the fax-quality > > scan. But I have some questions about it... > > >

Hi, sorry for the delay, I've been swamped lately :-/ On Fri, 10 Mar 2006, Eric Kidd wrote: > Thanks for your advice! I did get everything working (eventually) by pasting > the following code into the Makefile for HowToUseJIT: > > .PHONY: dump-config > dump-config: > @echo Compile: $(Compile.CXX) > @echo Link: $(Link) > @echo Libs:

Hello, I'm trying to avoid having to design my own IR for a hobby language that needs safety guarantees similar to those of Java. Have there been any plans or attempts to write a safety verifier for llvm object code or define a set of easily verifiable instructions that can be translated to llvm quickly?

Dear John, thanks! I was irritated by the path of the header file/declaration. It is not like the definition in a subdirectory. Sorry my fault. Is there an overview where classes and link options are mapped to each other? Kind regards, Nico On Jan 4, 2009, at 4:07 PM, John Criswell wrote: > Dear Nico, > > I believe you need to add LLVMipa to the list of libraries to link >

On Mar 16, 2006, at 2:16 AM, Chris Lattner wrote: > On Wed, 15 Mar 2006, Eric Kidd wrote: >> OK! Would something like the following interface be a reasonable >> first approach? >> >> llvm-config (--cxxflags | --ldflags | --libs) (all | jit) >> --cxxflags: Flags to use when compiling C++ source code. >> --ldflags: Linker flags to use when linking

Hi all! I have installed LLVM 1.9 under FreeBSD and read the documentation. Problem: examples/HowToUseJIT fails to compile. I entered the following command in the directory /usr/home/x/llvm1.9/examples/HowToUseJIT : gmake ENABLE_OPTIMIZED=0 It stops after producing object files (.o) without comment. When I enter the following (from the documentation): g++ `llvm-config --ldflags` -o HowToUseJIT

Hi! I've started looking porting our application which uses LLVM JIT to using LLVM 9 (9.0.1). To begin, I tried running the HowToUseJIT.cpp (example directory) program and it fails with a segfault: ./HowToUseJIT We just constructed this LLVM module: ; ModuleID = 'test' source_filename = "test" Running foo: Segmentation fault (core dumped) Running it through GDB:

Hi This llvm-config --libs engine bcreader scalaropts <http://llvm.org/cmds/llvm-config.html> in website http://llvm.org/cmds/llvm-config.html But actually bcreader components is not there anymore. The new name of it is bitreader. I thinks this webpage may need to update and also. If i do "llvm-config --help". It will also show wrong component name in examples g++

On Wed, 15 Mar 2006, Eric Kidd wrote: > On Mar 14, 2006, at 2:22 PM, Chris Lattner wrote: >>> Gnome (and many other Unix projects with massively ugly dependencies) can >>> be linked trivially using a "foo-config" script. If LLVM had something >>> similar, it might save new LLVM developers several hours of digging >>> through manuals and

On Sat, 17 Dec 2005, Martin [iso-8859-1] Pärtel wrote: > I'm trying to avoid having to design my own IR for a hobby language that needs > safety guarantees similar to those of Java. Have there been any plans or > attempts to write a safety verifier for llvm object code or define a set of > easily verifiable instructions that can be translated to llvm quickly? Check out SAFECode:

Hi, all I found the example code examples/HowToUseJIT.cpp also shows the same error. Attachment is the LLVM module created by HowToUseJIT. And here is the error, Running foo: %X4<def> = LDtoc <ga:@add1>, %X2 UNREACHABLE executed! Stack dump: 0. Running pass 'PowerPC Machine Code Emitter' on function '@foo' Aborted Currently, I use gdb try to track down

Le Sun, Nov 07, 2004 at 04:14:19PM -0600, Misha Brukman écrivait/wrote: > On Sun, Nov 07, 2004 at 11:04:58PM +0100, Basile STARYNKEVITCH wrote: Basile>> First, I am extremely confused by the terminology. IMHO, the runtime Basile>> libraries would include (from my JIT only perspective) Basile>> 1. all the LLVM libraries required to JIT-generate machine code, and

Excuse the long post, Chris Lattner wrote: > On Fri, 11 Mar 2005, Marc Ordinas i Llopis wrote: > >> Sorry if this is obvious. >> I'm trying to link LLVM-generated code with LLVM itself, and don't >> know how to do it. Just as a little test, I've tried compiling the >> example HowToUseJIT.cpp using llvm-g++, but I get tons of errors. >> >>

>> Patch attached. >> >> This patch with header installation patch ( >> http://mail.cs.uiuc.edu/pipermail/llvmdev/2005-February/003300.html ) >> let external project (I am test it at my YAFL frontend for LLVM) build >> using installed LLVM version instead using LLVM obj/src dirs. > > I think the patch looks basically sane. The one wierd thing I notice

llvm-bounces at cs.uiuc.edu wrote: > > ------------------------------------------------------------------------ > > Subject: > Fw: (by sospeng at tom.com)something is wrong , when compiling llvm on debian > From: > "4" <sospeng at tom.com> > Date: > Mon, 29 Aug 2005 20:05:46 +0800 (CST) > To: > llvmdev at cs.uiuc.edu > > To: > llvmdev at