Hello, I was wondering if there is someone already working on putting the new OrcJIT APIs in the LLVM-C bindings? Also, is there a general consensus to also add C bindings when new major features are added? Hayden -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150201/061f5949/attachment.html>
On Sun, Feb 1, 2015 at 10:58 AM, Hayden Livingston <halivingston at gmail.com> wrote:> Hello, > > I was wondering if there is someone already working on putting the new > OrcJIT APIs in the LLVM-C bindings? > > Also, is there a general consensus to also add C bindings when new major > features are added? >Generally not, so far as I know. Things are added to the C bindings on an as-needed basis, generally.> > Hayden > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150201/883172b6/attachment.html>
Thanks, David. I'd be happy to add the bindings .. is there a general way we add them? Or do you just scrub the API and make sensible judgements to the API? On Sun, Feb 1, 2015 at 1:55 PM, David Blaikie <dblaikie at gmail.com> wrote:> > > On Sun, Feb 1, 2015 at 10:58 AM, Hayden Livingston <halivingston at gmail.com > > wrote: > >> Hello, >> >> I was wondering if there is someone already working on putting the new >> OrcJIT APIs in the LLVM-C bindings? >> >> Also, is there a general consensus to also add C bindings when new major >> features are added? >> > > Generally not, so far as I know. Things are added to the C bindings on an > as-needed basis, generally. > > >> >> Hayden >> >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> >> >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150203/eefac331/attachment.html>
HI Hayden, There's no plan to expose any of the Orc APIs directly just yet - they're still very experimental. We could add a call to opt-in to using OrcMCJITReplacement rather than MCJIT though. Cheers, Lang.> On Feb 1, 2015, at 10:58 AM, Hayden Livingston <halivingston at gmail.com> wrote: > > Hello, > > I was wondering if there is someone already working on putting the new OrcJIT APIs in the LLVM-C bindings? > > Also, is there a general consensus to also add C bindings when new major features are added? > > Hayden > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Maybe Matching Threads
- [LLVMdev] OrcJIT in LLVM C bindings
- [LLVMdev] How will OrcJIT guarantee thread-safety when a function is asked to be re generated?
- [LLVMdev] How will OrcJIT guarantee thread-safety when a function is asked to be re generated?
- [LLVMdev] [RFC] Developer Policy for LLVM C API
- [LLVMdev] stability of llvm ir across releases