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>
On Tue, Feb 3, 2015 at 3:51 PM, Hayden Livingston <halivingston at gmail.com> wrote:> 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? >Pretty much that, I suppose - that's my rough understanding anyway.> > 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/9bdf38e8/attachment.html>
On Tue, Feb 3, 2015 at 4:00 PM, David Blaikie <dblaikie at gmail.com> wrote:> > > On Tue, Feb 3, 2015 at 3:51 PM, Hayden Livingston <halivingston at gmail.com> > wrote: > >> 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? >> > > Pretty much that, I suppose - that's my rough understanding anyway. >That said, ORC is a relatively new API that may be in flux and the C API does come with a rather strong (I forget if we've clarified this & made different guarantees) guarantee of backwards compatibility, so it might not be appropriate to expose such a detailed API especially for a new/experimental piece of code - not sure.> > >> >> 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/88f4a710/attachment.html>