<html>
<head>
<base href="https://llvm.org/bugs/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW " title="NEW --- - Improvements to the LLVM C API for the JIT" href="https://urldefense.proofpoint.com/v2/url?u=https-3A__llvm.org_bugs_show-5Fbug.cgi-3Fid-3D24224&d=AwMBaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=pF93YEPyB-J_PERP4DUZOJDzFVX5ZQ57vQk33wu0vio&m=AFq_i8jfRUMgznOpGVGgym0NPzcLtICvzockqn_CL7I&s=ESDkywkNES8tqWx6wJ19vF6B-c661-fEKc03cxaavc0&e=">24224</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Improvements to the LLVM C API for the JIT
</td>
</tr>
<tr>
<th>Product</th>
<td>libraries
</td>
</tr>
<tr>
<th>Version</th>
<td>trunk
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>Generic Execution Engine Support
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>lhames@gmail.com
</td>
</tr>
<tr>
<th>CC</th>
<td>llvmbugs@cs.uiuc.edu
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr></table>
<p>
<div>
<pre>This bug is an umbrella for discussion on improvements to the LLVM C API for
LLVM JIT support (both MCJIT and Orc).
The C API for the JIT in LLVM is a little long in the tooth. It still has some
hangovers from the legacy JIT, is still missing support for some MCJIT
functionality, and has no support whatsoever for the Orc JIT. We should
re-evaluate it, determine what (if anything) can be safely removed, and what
new features people would like to see. There is no schedule for this work, but
any changes will be happening in LLVM 3.8 or later.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>