diff options
author | Reid Spencer <rspencer@reidspencer.com> | 2005-07-12 16:36:24 +0000 |
---|---|---|
committer | Reid Spencer <rspencer@reidspencer.com> | 2005-07-12 16:36:24 +0000 |
commit | fce2ddcefd297630e8983a4e8971451d07c9a888 (patch) | |
tree | 5ceb5cd9e226d5ccca897e29803bcb6aed1829f7 /docs/ReleaseNotes.html | |
parent | ee448630bdf7eb6037fe2c50518d32010c433ca3 (diff) | |
download | external_llvm-fce2ddcefd297630e8983a4e8971451d07c9a888.zip external_llvm-fce2ddcefd297630e8983a4e8971451d07c9a888.tar.gz external_llvm-fce2ddcefd297630e8983a4e8971451d07c9a888.tar.bz2 |
Update release notes regarding thread-safe JIT.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@22405 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/ReleaseNotes.html')
-rw-r--r-- | docs/ReleaseNotes.html | 12 |
1 files changed, 8 insertions, 4 deletions
diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html index fa35778..684542b 100644 --- a/docs/ReleaseNotes.html +++ b/docs/ReleaseNotes.html @@ -77,6 +77,14 @@ a large number of new features and enhancements, described below.</p> <h1> See <a href="/releases/1.5/docs/ReleaseNotes.html">LLVM 1.5 Release Notes</a> </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> <!--=========================================================================--> @@ -180,10 +188,6 @@ components, please contact us on the llvmdev list.</p> <ul> <li>In the JIT, <tt>dlsym()</tt> on a symbol compiled by the JIT will not 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 mark values live across a setjmp as volatile</a>. This missing feature only affects targets whose setjmp/longjmp libraries do not save and restore |