<html>
<head>
<base href="http://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 --- - MCJIT does not support multiple modules"
href="http://llvm.org/bugs/show_bug.cgi?id=16795">16795</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>MCJIT does not support multiple modules
</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>andrew.kaylor@intel.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>In order for a single instance of MCJIT to be able to allow users to add new
code after compiling, MCJIT must support multiple modules.
Currently MCJIT assumes that it will only ever need to work with one module.
Several member variables reflect the state of that module, and these will need
to be re-worked to track the state of multiple modules.
In addition, MCJIT should attempt to provide cross-module linking for the
modules it owns, while still allowing the user to override this behavior if
necessary.
The code used in the MCJIT implementation of Kaleidoscope (see
<a href="http://blog.llvm.org/2013/07/kaleidoscope-performance-with-mcjit.html">http://blog.llvm.org/2013/07/kaleidoscope-performance-with-mcjit.html</a>) may be
helpful in guiding this feature development.</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>