similar to: [LLVMdev] Python-LLVM bindings updated

Hi Jarno, This is great! We would absolutely love to have python bindings for LLVM. From the look of your patch, I think we want this to become an LLVM project since it has configuration and compiler support that is new to the main LLVM repository. We don't want the main LLVM libraries to be dependent on Boost or Python. So, there's a couple things we need to have you do before this

Hi, some discussion below. Reid wrote: > 3. Fix your Makefile to build a shared library properly. You have set > TOOLNAME which is for building an executable tool not a shared > library. You need to set LIBRARYNAME=..., not TOOLNAME=... I remember having failed to build a functioning Python extension module with LIBRARYNAME and SHARED_LIBRARY flags. Anyway, I cannot remember

Hi all, There's a place where I can find an updated version of the bindings versus the actual CVS? There's a CVS store for them? I cannot contact Jarno (wrong mail address...) Thanks in advance! --- Paolo On May 22, 2005, at 11:45 AM, js.nospam at wolke7.net wrote: > Hi, > > I've updated the Python LLVM bindings for LLVM 1.5 (attached).

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

Hi Takumi, > Any feedbacks are welcome. > Have fun! This seems to be pretty useful addition to LLVM on windows! And it seems the only painless way to make plugins working, yay! For me the patch looks pretty good. One minor thing: could you please rename SharedDir => SharedLibDir Thanks! -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg

Good summer, all! This patch enables ENABLE_SHARED=1 to build DLL based LLVM toolchain. I have checked this on Cygwin-1.5, Cygwin-1.7, mingw(msysgit) and mingw-cross-fedora12. I can separate this patch into some parts; cleanups, adding definitions and adding rules. Any feedbacks are welcome. Have fun! ...Takumi * Pros - reduction of linking time of toolchain. - capability of -load

If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.

Hi, In buildling XPS using LLVM's makefile system, I'm finding that there's a few things lacking in our support for LLVM-based projects. The items below should help but may require changes to project makefiles. I thought I'd check before just going and doing it. 1. Various autoconf generated variables (e.g. abs_top_srcdir) are set in the makefiles but not used. They

Hi, I would like to share my experimental LLVM API Python bindings with the LLVM enthusiasts. I have created Boost.Python wrappers largely for the VMCore interface and other selected interfaces (e.g. ExecutionEngine). The bindings provide direct runtime access to the LLVM bytecode and JIT execution features from Python. The bindings are complete enough so that one can e.g. run the Fibonacci

Jarno, This looks like it could be very valuable - thanks for making it available. Just out of curiosity, do you have any specific uses in mind for which you created these bindings? --Vikram http://www.cs.uiuc.edu/~vadve http://llvm.cs.uiuc.edu/ On Feb 23, 2005, at 5:21 PM, Jarno Seppänen wrote: > Hi, > > I would like to share my experimental LLVM API Python bindings with >

The proposed makefile changes have been committed. If you are working from CVS head and you use the LLVM Makefile System in your own project, please make a note of the following: 1. If your makefiles use any BUILD_* variables, they now need to be prefixed with PROJ_ instead of BUILD_. For example, BUILD_SRC_ROOT is now PROJ_SRC_ROOT. 2. There are additional requirements

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

The proposed makefile changes have been committed. If you are working from CVS head and you use the LLVM Makefile System in your own project, please make a note of the following: 1. If your makefiles use any BUILD_* variables, they now need to be prefixed with PROJ_ instead of BUILD_. For example, BUILD_SRC_ROOT is now PROJ_SRC_ROOT. 2. There are additional requirements for projects.

The llvm.cs.uiuc.edu site does not seem to be updating at the moment so it contains the old instructions. If you're looking for the new instructions on the Projects.html page, you can view them here: http://illuvium.net/docs/Projects.html Reid. On Sat, 2005-01-15 at 18:30, Reid Spencer wrote: > The proposed makefile changes have been committed. If you are working > from CVS head and

Is it possible to write LLVM IR but not using C++? I'm exceedingly terrible at C++. I was thinking, isn't it possible to write the IR using Java? I effectively have emit some sort of binary op codes to be passed into llvm right? The same thing for if I wanted to integrate a GC? Could the interfacing be done in any other language? -------------- next part -------------- An HTML

Don't you have the same problem with other atoms, e.g. variable names? This sounds like something that should be implemented in the language's runtime library. On May 4, 2014 7:15 PM, "Alexander Popolitov" <popolit at gmail.com> wrote: > Hi everyone! > > I'm trying to implement lisp's funcall function, which roughly calls a > function, name of which

Hi, here's a brief update of the status of the python bindings. Recently I've updated them with the API changes in LLVM 1.6 and split the submodules (VMCore, ExecutionEngine, etc.) into separate builds, making the dynamic libraries smaller. I agree that the bindings should be in a CVS somewhere, and last year there was some discussion of putting them in the llvm tree. The python

On Wed, Jan 9, 2019 at 9:38 AM Mehdi AMINI <joker.eph at gmail.com> wrote: > > > > On Fri, Jan 4, 2019 at 3:15 PM Davide Italiano via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> I would like to propose, based on a previous discussion on llvm-dev, >> the following change. >> https://reviews.llvm.org/D56337 >> >> The

Hello all, I am involved in a compiler project for Transport Triggered Architectures (think VLIW and you are pretty close), and we are considering using LLVM. Browsing the list archives, I noticed an announcement of Python bindings for LLVM 1.5. Does anyone know the current status of the bindings? -- Pertti

"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