similar to: [LLVMdev] "LLVM powered Mono"

Sorry for being a newbie on the matter, but could someone explain the comment (in response to: "Considering it [LLVM] supports three other languages with try/catch clauses just fine (C++, Ada, and now, Java), I think it would be incorrect to say "it is not able to support some of the features"."): ------------------------------ The issue is that the exception handling as

Hi, mono implements its own exception handling mostly for historical reasons, and for compatibility with ms.net (as ms.net exception handling is based on windows seh, and I'm not sure the linux c++ abi can implement all .net exception handling features like filter clauses). So to make this work with llvm, we would have to throw out mono's current exception handling system, which we are

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

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, 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. Thanks, Paul

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

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

Hello Paul, The one I downloaded from http://llvm.org/devmtg/2008-08/Begeman_EfficientJIT.pdf seemed to have been formatted with white text on a grey background. Maybe that's the version you need. --Sam ----- Original Message ---- > From: Paul Melis <llvm at assumetheposition.nl> > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Sent: Wednesday, May 6,

On Wed, May 13, 2009 at 6:35 AM, Paul Melis <llvm at assumetheposition.nl> wrote: > 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