From fce2ddcefd297630e8983a4e8971451d07c9a888 Mon Sep 17 00:00:00 2001
From: Reid Spencer
Date: Tue, 12 Jul 2005 16:36:24 +0000
Subject: [PATCH] Update release notes regarding thread-safe JIT.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@22405 91177308-0d34-0410-b5e6-96231b3b80d8
---
docs/ReleaseNotes.html | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/docs/ReleaseNotes.html b/docs/ReleaseNotes.html
index fa357786dc3..684542bf017 100644
--- a/docs/ReleaseNotes.html
+++ b/docs/ReleaseNotes.html
@@ -77,6 +77,14 @@ a large number of new features and enhancements, described below.
+
+ - 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
+ PR418 and
+ PR540 for the details.
+
+
@@ -180,10 +188,6 @@ components, please contact us on the llvmdev list.
- In the JIT, dlsym() on a symbol compiled by the JIT will not
work.
- - 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.
-
- The lower-invoke pass does not
mark values live across a setjmp as volatile. This missing feature
only affects targets whose setjmp/longjmp libraries do not save and restore