RPCSX/llvm
1
0
Fork 0
mirror of https://github.com/RPCSX/llvm.git synced 2025-02-24 07:01:35 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update release notes regarding thread-safe JIT.

Browse Source 
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@22405 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Reid Spencer 2005-07-12 16:36:24 +00:00
parent ee448630bd
commit fce2ddcefd
1 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/ReleaseNotes.html
View File

@ -77,6 +77,14 @@ a large number of new features and enhancements, described below.</p>
<h1> <h1>
See <a href="/releases/1.5/docs/ReleaseNotes.html">LLVM 1.5 Release Notes</a> See <a href="/releases/1.5/docs/ReleaseNotes.html">LLVM 1.5 Release Notes</a>
</h1> </h1>
<ol>
<li>The JIT now uses mutexes to protect its internal data structures. This
allows multi-threaded programs to be run from the JIT or interpreter without
corruption of the internal data structures. See
<a href="http://llvm.cs.uiuc.edu/PR418">PR418</a> and
<a href="http://llvm.cs.uiuc.edu/PR540">PR540</a> for the details.
</li>
</ol>
</div> </div>
<!--=========================================================================--> <!--=========================================================================-->
@ -180,10 +188,6 @@ components, please contact us on the llvmdev list.</p>
<ul> <ul>
<li>In the JIT, <tt>dlsym()</tt> on a symbol compiled by the JIT will not <li>In the JIT, <tt>dlsym()</tt> on a symbol compiled by the JIT will not
work.</li> work.</li>
<li>The JIT does not use mutexes to protect its internal data structures. As
such, execution of a threaded program could cause these data structures to be
corrupted.
</li>
<li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not <li><a href="http://llvm.cs.uiuc.edu/PR240">The lower-invoke pass does not
mark values live across a setjmp as volatile</a>. This missing feature mark values live across a setjmp as volatile</a>. This missing feature
only affects targets whose setjmp/longjmp libraries do not save and restore only affects targets whose setjmp/longjmp libraries do not save and restore