maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

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

This commit is contained in:
Lang Hames 2022-03-26 13:14:26 -07:00
parent 824a73bbfa
commit 34b547dfbf
1 changed files with 5 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
llvm/docs/ORCv2.rst
View File

@ -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 difficult 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
difficult to read, and usually only good for one session.
Roadmap
=======