[llvm] 34b547d - [docs][ORC] Simplify paragraph on hardcoding process addresses.

[Lang Hames via llvm-commits]

Author: Lang Hames
Date: 2022-03-26T13:14:26-07:00
New Revision: 34b547dfbf7660575b815e39de5bb043857579ca

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

LOG: [docs][ORC] Simplify paragraph on hardcoding process addresses.

Added: 
    

Modified: 
    llvm/docs/ORCv2.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/ORCv2.rst b/llvm/docs/ORCv2.rst
index 2d03ba57bb326..78bf7a084ccc3 100644
--- a/llvm/docs/ORCv2.rst
+++ b/llvm/docs/ORCv2.rst
@@ -854,13 +854,11 @@ example, to expose an allowed set of symbols from the main process:
     // and contained in the list.
     CompileLayer.add(JD, loadModule(...));
 
-As an aside, it's worth pointing out that references to process or library
-symbols could simply be hardcoded into your IR or object files using the
-symbols' raw addresses. Symbolic resolution using the JIT symbol tables should
-usually be preferred though: Both methods require you to resolve the process
-symbol addresses, but symbolic resolution via the JIT symbol tables keeps the
-IR and objects readable and reusable in subsequent JIT sessions. Hardcoded
-addresses are 
diff icult to read, and usually only good for one session.
+References to process or library symbols could also be hardcoded into your IR
+or object files using the symbols' raw addresses, however symbolic resolution
+using the JIT symbol tables should be preferred: it keeps the IR and objects
+readable and reusable in subsequent JIT sessions. Hardcoded addresses are
+
diff icult to read, and usually only good for one session.
 
 Roadmap
 =======