similar to: [LLVMdev] OT: Python on LLVM

On Thu, Mar 26, 2009 at 8:20 AM, Paul Melis <llvm at assumetheposition.nl> wrote: > 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

Hi all, First, I just want to say thank you for the excellent LLVM project. I have been playing with LLVM for the first part of this year and have been quite impressed with what I've seen and what is possible. I've been coding for a long time, but haven't had this much fun since I first learned Python. The work you have done has opened the door for a tremendous amount of

In Unladen Swallow we (intend to) compile each function as we determine it's hot. To "compile" a function means to translate it from CPython bytecode to LLVM IR, optimize the IR using a FunctionPassManager, and JIT the IR to machine code. We'd like to include inlining among our optimizations. Currently the Inliner is a CallGraphSCCPass, which can only be run by the

The only VHDL to LLVM project that I know of is nvc. [0] I haven't tried it personally and from a cursory look through the source it seems like there is a LLVM backend and a "native" backend (not sure what that means). If you're really crazy you might want to see if you could massage GHDL [1] (VHDL GCC frontend) + DragonEgg [2] (LLVM backend for GCC) to get you LLVM IR. I'm

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

On May 26, 2009, at 3:15 PM, Jeffrey Yasskin wrote: > In Unladen Swallow we (intend to) compile each function as we > determine it's hot. To "compile" a function means to translate it from > CPython bytecode to LLVM IR, optimize the IR using a > FunctionPassManager, and JIT the IR to machine code. We'd like to > include inlining among our optimizations. Currently

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

Not sure, but it seems the page contains a number of out-of-date entries: Pypy => pypy.org (link stale) plus: there is no llvm backend for pypy at the moment (although LLVM backends have been attempted a number of times, all seem to have failed) Unladen Swallow => not being developed since 2011 (http://qinsb.blogspot.com/2011/03/unladen-swallow-retrospective.html) TIA, Andreas The

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

Hello Duncan, > thanks for your interesting email. Do you understand why PyPy is no longer > using LLVM, and why Unladen Swallow died? Does LLVM need to be improved in > some way? The answers to all these questions are linked: LLVM is not fast enough (for a JIT). Of course this is not the whole story, but it is the LLVM-relevant part. Let's have a look at some random performance

I want to connect each llvm ir for example: 1. Turn C/C++ language into C_llvmIR assembly language using Clang 2. Turn Fortran language into Fortran_llvmIR assembly language using Dragonegg 3. Turn Python language into Python_llvmIR assembly language using Unladen-Swallow 4. Connect each llvm IR Is this possible? Wonjun, Choi -------------- next part -------------- An HTML attachment was

According to http://llvm.org/docs/DebuggingJITedCode.html only ELF objects are supported for gdb support of JIT generated code. Is this still true, or are Mach-O files now supported in 2.7 trunk? Thanks in advance Garrison

"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

Hi Travis, ... > LLVM is still very relevant to Python because of projects like Numba --- but you > should know that PyPy is no longer using LLVM and Unladen Swallow has not been > worked on for several years. The future of LLVM and Python I think is very > bright --- especially for the scientific and data-analysis user-base. thanks for your interesting email. Do you understand

If you didn't catch it, there has been a recent post to the mailing list that seems like it might be relevant to your interests: <http://lists.cs.uiuc.edu/pipermail/llvmdev/2012-June/051298.html> Direct link to the project page: <http://code.google.com/p/pymothoa/> --Sean Silva On Wed, Jul 11, 2012 at 12:37 AM, Travis Oliphant <travis at continuum.io> wrote: > Hi all,