similar to: [LLVMdev] Programmatically setting command line options?

On Sun, Jun 7, 2009 at 1:48 AM, Paul Melis<llvm at assumetheposition.nl> wrote: > Hello, > > Is there currently a way to set options, like -time-passes or -regalloc > from C++? I looked at the code in lib/Support/CommandLine.cpp, but the > stuff that comes closest to providing such functionality (mostly > GetOptionInfo()) is marked static. You can manipulate the

Hello all, Does anyone have any inside why I can't get the below simple C API test to link? This is on a 32-bit Gentoo Linux system and LLVM TOT which was compiled with enable-optimized, gcc is 4.3.2. 15:26|melis at juggle2:~/c/llvmpy> cat t.c #include "llvm-c/Core.h" int main() { LLVMContextRef ctx; ctx = LLVMContextCreate(); return 0; } 15:29|melis at

Paul Melis <llvm at assumetheposition.nl> writes: > It seems that the llvm-config generated when building through CMake does > not contain -lpthread on my 32-bit Core2Duo Gentoo Linux system (even > though I configured with LLVM_ENABLE_PTHREADS). I get missing symbols > during linking of e.g. the JIT tutorial code: [snip] This should be fixed now. Now about this one: >

Paul Melis <llvm at assumetheposition.nl> writes: > Hi, just chiming in here... > > Óscar Fuentes wrote: >> [...] >> >> This is a simple guide for using cmake with LLVM: >> >> http://www.llvm.org/docs/CMake.html >> >> The makefiles distributed with LLVM have nothing to do with cmake. >>From the few times I tried building LLVM with

Hi Andrew, On 04/19/10 14:27, Andrew Friedley wrote: > Sorry for responding to my own message but I would really appreciate > some help with this. > > Looking through the documentation again this morning I noticed that > setSchedulingPreference is a protected method of LLVMTargetLowering, so > it looks like it's not something I can call directly anyway. > Furthermore

On 04/27/10 00:20, Talin wrote: > On Mon, Apr 26, 2010 at 12:44 AM, Paul Melis > <llvm at assumetheposition.nl <mailto:llvm at assumetheposition.nl>> wrote: > > Hi, > > Talin wrote: > > I'm a little confused as to the rules for the arguments to > llvm.gcroot, > > which says it must be a pointer alloca. I'm not sure whether

Óscar Fuentes wrote: > Paul Melis <llvm at assumetheposition.nl> writes: > > >> It seems that the llvm-config generated when building through CMake does >> not contain -lpthread on my 32-bit Core2Duo Gentoo Linux system (even >> though I configured with LLVM_ENABLE_PTHREADS). I get missing symbols >> during linking of e.g. the JIT tutorial code: >>

Hi Oscar, Óscar Fuentes wrote: > Paul Melis <llvm at assumetheposition.nl> writes: > > [snip] > > Thanks! Fixed. > > BTW, bug reports are welcome. > It seems that the llvm-config generated when building through CMake does not contain -lpthread on my 32-bit Core2Duo Gentoo Linux system (even though I configured with LLVM_ENABLE_PTHREADS). I get missing symbols

On 04/29/10 21:27, Talin wrote: > On Wed, Apr 28, 2010 at 12:16 PM, Paul Melis > <llvm at assumetheposition.nl <mailto:llvm at assumetheposition.nl>> wrote: > > On 04/27/10 00:20, Talin wrote: >> On Mon, Apr 26, 2010 at 12:44 AM, Paul Melis >> <llvm at assumetheposition.nl <mailto:llvm at assumetheposition.nl>> wrote: >> >>

On Wed, Apr 28, 2010 at 12:16 PM, Paul Melis <llvm at assumetheposition.nl>wrote: > On 04/27/10 00:20, Talin wrote: > > On Mon, Apr 26, 2010 at 12:44 AM, Paul Melis <llvm at assumetheposition.nl>wrote: > >> Hi, >> >> Talin wrote: >> > I'm a little confused as to the rules for the arguments to llvm.gcroot, >> > which says it must be

Hi, Slightly off-topic (as it's not directly about using or developing LLVM): http://code.google.com/p/unladen-swallow/wiki/ProjectPlan "Our long-term proposal is to replace CPython's custom virtual machine with a JIT built on top of LLVM, while leaving the rest of the Python runtime relatively intact." Just curious, has anyone here heard more about this project? Regards,

"Paul Melis" <llvm at assumetheposition.nl> writes: > 15:29|melis at juggle2:~/c/llvmpy> gcc -W -Wall -o blah `llvm-config --cflags > --ldflags --libs all` t.c > /tmp/ccs4MbKp.o: In function `main': > t.c:(.text+0x21): undefined reference to `LLVMContextCreate' > collect2: ld returned 1 exit status > > 15:29|melis at juggle2:~/c/llvmpy> nm

Well well, LLVM seems to be everywhere these days :) >From the OpenCL SDK release notes: NOTICE: Portions of the NVIDIA system software contain components licensed from third parties under the following terms: Clang & LLVM: Copyright (c) 2003-2008 University of Illinois at Urbana-Champaign. All rights reserved. Portions of LLVM's System library: Copyright (C)

Mike Stump wrote: > On May 22, 2009, at 3:27 PM, Óscar Fuentes wrote: > >> Sadly, this is not possible in general. >> > > To a hacker, few things are not possible. :-) > > >> The files generated by CMake are not guaranteed to be relocatable >> (they use absolute paths). >> > > A problem merely waiting for someone to fix it.

Hello, i want to use the Scalarizer pass. (http://llvm.org/doxygen/Scalarizer_8cpp_source.html). This pass exposes the "scalarize-load-store"(default false) option on the command line. For my use-case i want to always enable this option. How can i enable this option programmatically? Thank you

Hi, Chris Lattner wrote: > On May 6, 2009, at 10:53 AM, Villmow, Micah wrote: >> Yeah, I found that out, which is why I was hoping some kind of >> attribute existed that the compiler knew about. >> We might go the path of modifying llvm-link to only link in functions >> that are required as that seems to be the most optimal way of doing it. > > If you care about

Looks like LLVM support in Mono has matured to the point they're willing to advertise it: http://tirania.org/blog/archive/2009/Jul-16.html Paul PS Zoltan, sorry if I stole your opportunity to break the news :)

Hi, Talin wrote: > I'm a little confused as to the rules for the arguments to llvm.gcroot, > which says it must be a pointer alloca. I'm not sure whether that means it > must be an alloca (which is always a pointer by definition) or an alloca > *of* a pointer. I'm pretty sure it should be "alloca of a pointer", as the first argument of llvm.gcroot has type i8**.

On Mon, Apr 26, 2010 at 12:44 AM, Paul Melis <llvm at assumetheposition.nl>wrote: > Hi, > > Talin wrote: > > I'm a little confused as to the rules for the arguments to llvm.gcroot, > > which says it must be a pointer alloca. I'm not sure whether that means > it > > must be an alloca (which is always a pointer by definition) or an alloca > > *of* a

> I'm linking a program (my ellsif driver) that basically brings in most > of the LLVM stuff: bitcode reading, optimizations, linking, and target > code generation. > > All of a sudden, I'm getting the following when I run: > [~/elsa/ellsif] dev% ./ellsif -v test/ofmt.i test/sieve.i -time-actions > -O5 > <premain>: CommandLine Error: Argument