similar to: [LLVMdev] Troubles with llvm.gcroot and exception handling

[Forgot to include llvmdev in my reply, sending a second time] Hi Duncan, Duncan Sands wrote: >> 22:40|melis at juggle2:~/projects/llvm_gc> llc root.ll >> 22:40|melis at juggle2:~/projects/llvm_gc> gcc -o r root.s >> /usr/lib/gcc/i686-pc-linux-gnu/4.3.4/../../../../i686-pc-linux-gnu/bin/ld: >> error in /tmp/ccGhPZDb.o(.eh_frame); no .eh_frame_hdr table will be

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: >

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

Ó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: >>

The langref says for the 'add' instruction: Syntax: <result> = add <ty> <op1>, <op2> ; yields {ty}:result <result> = nuw add <ty> <op1>, <op2> ; yields {ty}:result <result> = nsw add <ty> <op1>, <op2> ; yields {ty}:result <result> = nuw nsw add <ty> <op1>, <op2> ;

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 wrote: > Paul Melis wrote: > >> Jim Grosbach wrote: >> >>> On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: >>> >>> >>>> Hello, >>>> >>>> Bill Wendling wrote: >>>> >>>>> Before we had buildbots, a random patch would break the system. It >>>>>

"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

Paul Melis wrote: > Ó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

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

Paul Melis wrote: > Jim Grosbach wrote: >> >> On Aug 30, 2009, at 10:18 AM, Paul Melis wrote: >> >>> Hello, >>> >>> Bill Wendling wrote: >>>> Before we had buildbots, a random patch would break the system. It >>>> would sometimes take a whole day to determine which patch broke it. >>> I see the buildbots are currently

"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

Chuck Robey wrote: >>>> >>>> >>> Uh? My FreeBSD installment has `make' and no `gmake'. `make' is indeed >>> BSD make. >>> > > In your FreeBSD system, do an "ls -d /var/db/pkg/gmake*" and see if any > directory shows up. If it does, then the only argument you can have is what > name you

Paul Melis wrote: > Hi, > > Óscar Fuentes wrote: >> Chuck Robey <chuckr at telenix.org> writes: >> >> >>>> Just checked that the makefiles generated by cmake work with `make' on >>>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>>> missing. >>>> >>> They

Hi, Óscar Fuentes wrote: > Chuck Robey <chuckr at telenix.org> writes: > > >>> Just checked that the makefiles generated by cmake work with `make' on >>> FreeBSD 7.2 x86. The build fails while building `opt' because libdl is >>> missing. >>> >> They absolutely do work, even on FreeBSD-current( I run that here), >>

This is an interesting problem. The GC code is being converted into 'invokes' instead of calls: define i32 @main() gc "shadow-stack" { entry: %gc_frame = alloca %gc_stackentry.main %gc_currhead = load %gc_stackentry** @llvm_gc_root_chain %gc_frame.map = getelementptr %gc_stackentry.main* %gc_frame, i32 0, i32 0, i32 1 store %gc_map* getelementptr inbounds (%gc_map.0*

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

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: >> >>

Hello, I've spent some time with the LLVM documentation and am beginning to grasp a few things, but I sometimes need very literal statements to actually understand things. My first question is about StackMaps: Is it true that llvm_gc_root_chain is an API? I've been trying to understand how exactly one accesses this structure and no where in the documentation does it mention this is a

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