llvm dev - Mar 2010 - [LLVMdev] Last chance to get anything into llvm-c and ocaml bindings

I've pretty much finished exposing all I wanted to llvm-c and the
ocaml bindings for the soon to be released 2.7. Does anyone need any
other functions exposed before the code freeze on the 7th?

Erick Tryzelaar <erick.tryzelaar <at> gmail.com> writes:
> 
> I've pretty much finished exposing all I wanted to llvm-c and the
> ocaml bindings for the soon to be released 2.7. Does anyone need any
> other functions exposed before the code freeze on the 7th?
> 

Hi Erick,

Can you make the following functions available in llvm-c.

createStandardFunctionPasses
createStandardModulePasses
createStandardLTOPasses

Thanks in advance, George

On Mar 3, 2010, at 20:44, Erick Tryzelaar wrote:
> 
> I've pretty much finished exposing all I wanted to llvm-c and the
> ocaml bindings for the soon to be released 2.7. Does anyone need any
> other functions exposed before the code freeze on the 7th?
Oh hey... I remember now.  There is one thing I probably won't get around to
doing myself until after the code freeze.

  (* Llvm_bitwriter *)
  val output_bitcode: out_channel -> Llvm.llmodule -> unit

It would, of course, be awesome if you could get that into the 2.7 train.


—
j h woodyatt <jhw at conjury.org>
http://jhw.vox.com/

On Fri, Mar 5, 2010 at 9:29 AM, james woodyatt <jhw at conjury.org>
wrote:
>
> Oh hey... I remember now.  There is one thing I probably won't get
around to doing myself until after the code freeze.
>
>  (* Llvm_bitwriter *)
>  val output_bitcode: out_channel -> Llvm.llmodule -> unit
>
> It would, of course, be awesome if you could get that into the 2.7 train.
Committed in r97858.

On Fri, Mar 5, 2010 at 5:53 AM, George Giorgidze <giorgidze at gmail.com>
wrote:
>
> Hi Erick,
>
> Can you make the following functions available in llvm-c.
>
> createStandardFunctionPasses
> createStandardModulePasses
> createStandardLTOPasses
>
> Thanks in advance, George
This is a little tricky, so I need some advice from the community.
First off, I'm not sure where it's appropriate to put these. For
llvm-c, most files live in a header named after the library that
includes the functions, and we don't have a corresponding place for
these functions. Perhaps they could go in a
llvm-c/Transforms/StandardPasses.h?

Second, createStandardModulePasses accepts an inlining pass an an
argument, but llvm-c doesn't expose a way to directly create any
passes. So, should I just not expose that argument, or should I add:

LLVMPassRef
LLVMCreateFunctionInliningPass
LLVMCreateAlwaysInlinerPass
LLVMCreatePartialInliningPass

But that seems silly just to expose those passes this way without all
the other passes and related functions. Does anyone have a better
suggestion?