[llvm] c7e64df - [docs] Fix formatting, clarify comment in ORCv2 doc

Lang Hames via llvm-commits llvm-commits at lists.llvm.org
Wed Nov 11 18:19:30 PST 2020


Author: Lang Hames
Date: 2020-11-12T13:11:01+11:00
New Revision: c7e64df445599e7a5f2ca33a448b64e9bfaf3f6f

URL: https://github.com/llvm/llvm-project/commit/c7e64df445599e7a5f2ca33a448b64e9bfaf3f6f
DIFF: https://github.com/llvm/llvm-project/commit/c7e64df445599e7a5f2ca33a448b64e9bfaf3f6f.diff

LOG: [docs] Fix formatting, clarify comment in ORCv2 doc

Added: 
    

Modified: 
    llvm/docs/ORCv2.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/ORCv2.rst b/llvm/docs/ORCv2.rst
index fca08a6dd7a5..e475b47a4d1a 100644
--- a/llvm/docs/ORCv2.rst
+++ b/llvm/docs/ORCv2.rst
@@ -811,12 +811,12 @@ Near Future Work
    (e.g. Objective C and Swift) and other JIT specific runtime code. This should
    be built in a similar manner to compiler-rt (possibly even as part of it).
 
-2. **Remote ``jit_dlopen`` / ``jit_dlclose``**
+2. **Remote jit_dlopen / jit_dlclose**
 
    To more fully mimic the environment that static programs operate in we would
-   like JIT'd code to be able to "dlopen" JITDylibs, running all of their
-   initializers on the current thread. This would require support from the runtime
-   library described above.
+   like JIT'd code to be able to "dlopen" and "dlclose" JITDylibs, running all of
+   their initializers/deinitializers on the current thread. This would require
+   support from the runtime library described above.
 
 3. **Debugging support**
 


        


More information about the llvm-commits mailing list