search for: waldenborg

Moving this to llvmdev. On Fri, Sep 20, 2013 at 08:26:41AM +0200, Anders Waldenborg wrote: > > > This avoids warnings when included in a application that > > > uses -Wstrict-prototypes. > > > > > > > Should we enable this warning in CFLAGS for LLVM builds to catch this > > sooner? > > It is a C-only warning, and AFAICS there is...

I like the idea, but I find the name confusing; I think it should have `llvm-c` or `c-api` somewhere in the name. This could also serve as a simple example of using the API. -- Sean Silva On Mon, Sep 23, 2013 at 4:00 PM, Anders Waldenborg <anders at 0x63.nu> wrote: > Moving this to llvmdev. > > On Fri, Sep 20, 2013 at 08:26:41AM +0200, Anders Waldenborg wrote: > > > > This avoids warnings when included in a application that > > > > uses -Wstrict-prototypes. > > > > > > > &...

At Fri, 16 Mar 2012 14:12:08 +0100, Christoph Grenz wrote: > > Hello, > > Am Donnerstag, 15. März 2012, 21:15:02 schrieb Gregory Szorc: > > There was some talk on IRC last week about desire for Python bindings to > > LLVM's Object.h C interface. So, I coded up some and you can now find > > some Python bindings in trunk at bindings/python. Currently, the >

Hi, I have a question regarding the metadata for compileunit debug info. I find a few things in it a bit strange, but maybe there it is a reason for it to be that way that I just don't understand (but if that is the case I guess the documentation needs to be clearer). Consider this C program: "int X;" Compiled with "clang -g" it debug metadata along these lines:

I think having this would be awesome! On Tue, Sep 24, 2013 at 4:11 AM, Anders Waldenborg <anders at 0x63.nu> wrote: > On Mon, Sep 23, 2013 at 07:48:45PM -0400, Sean Silva wrote: >> I like the idea, but I find the name confusing; I think it should have >> `llvm-c` or `c-api` somewhere in the name. This could also serve as a >> simple example of using the API....

On Mon, Sep 23, 2013 at 07:48:45PM -0400, Sean Silva wrote: > I like the idea, but I find the name confusing; I think it should have > `llvm-c` or `c-api` somewhere in the name. This could also serve as a > simple example of using the API. I had it as llvm-c-test first, then noticed that the shared library's directory was named "llvm-shlib". Yes, making sure it serves as

On Mon, Mar 19, 2012 at 10:44 AM, Anders Waldenborg <anders at 0x63.nu> wrote: > > * Auto generated vs manual ctypes declarations. > This is purely a cosmetic difference, as we both take the same approach of registering functions on a global/shared ctypes library instance. I think automatic is the way to go (just as long as the auto...

On 3/17/2012 4:14 PM, Anders Waldenborg wrote: > FYI: > > I've also been working on new python bindings. > > My bindings are written using ctypes (just like the in-tree > clang/cindex bindings). Most of Core.h is bound, and stuff from > ExecutionEngine.h, Analysis, BitReader, BitWriter. The have fairly > goo...

On Sun, Mar 18, 2012 at 09:52:12PM -0700, Gregory Szorc wrote: > The automatic generation of the Python ctypes interfaces using the Clang > Python bindings is pretty friggin cool! A nice side effect is that everything is added to the interface. So it is easy to add a small proxy over the lib that shows which parts of the llvm-c API that is exercised by the tests. (have that in my bindings)

Attached is what I got thus far. What I'm struggling with is proper integration in build system. What is in there is just wild guesses from my side, both on autoconf and cmake variants. It would be great if someone with proper knowledge of the buildsystems could have a look. Also I'm not sure how to properly handle compilation on msvc - clearly "-std=c11 -Wstrict-prototypes" is