search for: r191029

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. > > I

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

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

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 no C code in

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