<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Nov 2, 2013 at 9:04 PM, Peter Zotov <span dir="ltr"><<a href="mailto:whitequark@whitequark.org" target="_blank">whitequark@whitequark.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello folks.<br>
<br>
I'm very interested in improving LLVM's OCaml bindings. I have<br>
several nontrivial patches sitting on llvm-commits for several<br>
weeks, and so far there's been little interest in them.<br>
<br>
Could someone with a good understanding of OCaml please take<br>
a look at these?<br>
<br>
1) <a href="http://llvm-reviews.chandlerc.com/D1925" target="_blank">http://llvm-reviews.chandlerc.<u></u>com/D1925</a><br>
<br>
Every other function in OCaml bindings accepts context<br>
explicitly, would it be a legitimate change to make existing<br>
functions accept it as well? This would break the API.<br></blockquote><div><br></div><div>I don't really have a good idea of who uses these OCaml bindings API's. A good first step is probably to map out the landscape of the users of the API. Maybe browse research papers? I wouldn't expect to see many OCaml programs "in production" that depend on this API. Also, I'm not sure if we have a stated backwards compatibility policy for this API. Ultimately you probably just want to talk with all the API users you can scrape together.</div>
<div><br></div><div>-- Sean Silva</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2) <a href="http://llvm-reviews.chandlerc.com/D1926" target="_blank">http://llvm-reviews.chandlerc.<u></u>com/D1926</a><br>
<br>
I'd like to add garbage collection support to the API<br>
wherever safe, that's at least DataLayout.t and llmemorybuffer.<br>
This removes the need for .dispose. I could remove it and break<br>
the API or print a warning at runtime.<br>
<br>
3) <a href="http://llvm-reviews.chandlerc.com/D1927" target="_blank">http://llvm-reviews.chandlerc.<u></u>com/D1927</a><br>
<br>
In order to allow code generation from OCaml, I need to build<br>
a stub library per configured target. I'm not sure how to<br>
integrate it with LLVM's build system; my current solution seems<br>
very ad-hoc.<br>
<br>
I will update the patch to use Dynlink interface (this is the<br>
textbook use case for Dynlink), but conceptually this doesn't<br>
change the problem of interfacing with build system.<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
WBR, Peter Zotov.<br>
______________________________<u></u>_________________<br>
LLVM Developers mailing list<br>
<a href="mailto:LLVMdev@cs.uiuc.edu" target="_blank">LLVMdev@cs.uiuc.edu</a> <a href="http://llvm.cs.uiuc.edu" target="_blank">http://llvm.cs.uiuc.edu</a><br>
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev" target="_blank">http://lists.cs.uiuc.edu/<u></u>mailman/listinfo/llvmdev</a><br>
</font></span></blockquote></div><br></div></div>