search for: moritzmaxeiner

On Mar 13, 2013, at 6:40 AM, Moritz Maxeiner <moritzmaxeiner at googlemail.com> wrote: > Hi, > > If I write LLVM bindings for a language X, in which I obviously > need to at least use parts of the llvm-c headers (constants, enums, typedefs, function names and > signatures) do I need to include the LLVM copyright notice? > > Whereas...

While writing bindings to LLVM for another language via the c api I noticed that LLVMAlignment and LLVMStackAlignment do not use 1<<x like all the others, but 31<<x and 7<x respectively (see below, or here: http://llvm.org/docs/doxygen/html/Core_8h_source.html#l00148). It's likely this is as it is intended, but it does look out-of-place enough that I thought it might be a

On Mar 13, 2013, at 12:17 PM, Moritz Maxeiner <moritzmaxeiner at googlemail.com> wrote: > On 03/13/2013 07:26 PM, Chris Lattner wrote: >> LLVM's license includes a binary redistribution clause: >> http://llvm.org/docs/DeveloperPolicy.html#license > > Hi Chris, > > the problem with the binary redistribution clause is that t...

On 03/13/2013 07:26 PM, Chris Lattner wrote: > LLVM's license includes a binary redistribution clause: > http://llvm.org/docs/DeveloperPolicy.html#license Hi Chris, the problem with the binary redistribution clause is that the bindings will not be linked with any part of LLVM. The bindings will load an LLVM shared library (dll/so/dylib) at runtime and thus an application compiled

Hi, when building llvm as a shared library LLVMInitializeNativeTarget and co. (located in llvm/Support/TargetSelect) will not get exported as symbol into the shared library, because they are static inline. Since they are functions defined in the C API no one else inside LLVM calls them, which results in them not being exported. This is, of course, no problem for C programs using the C API,

Hi, If I write LLVM bindings for a language X, in which I obviously need to at least use parts of the llvm-c headers (constants, enums, typedefs, function names and signatures) do I need to include the LLVM copyright notice? Whereas llvm-c has multiple headers (e.g. Analysis.h, BitReader.h, Core.h, etc.) my bindings only have three files constants.d, types.d and functions.d which respectively

I would like to use the LLVM-C bindings to provide LLVM access with an OO-design in another language (D), e.g. map from the C API back up to a D API that closely resembles the original C++ API. Since I would like to have D (with its own exception system) to handle the IO, I need a new C API function (unless there is one and I haven't found it): LLVMBool

Thank you guys for the fast replies (!), now I can continue without worrying about it. -- Moritz On 2/17/2013 1:46 PM, Daniel Murphy wrote: > These values are masks for numbers. LLVMAlignment uses 5 bits, so the > mask is 31 (0b11111) and these bits (16-20) cannot be used by other > flags so the next available bit is 21. Same thing for LLVMStackAlignment. On 2/17/2013 1:53 PM,

Dear LLVM devs (and other subscribers), when building llvm as a shared library (so or dll, tested with both) and then performing objdump on the resulting library will reveal that LLVMInitializeNativeTarget does not get exported ("objdump -x libLLVM-3.3svn.so | grep LLVMInitializeNativeTarget" will return without any output). As far as I can tell this is because the function is