This option tells LLJIT to disable platform support explicitly: JITDylibs aren't scanned for special init/deinit symbols and no runtime API interposes are injected.
It's useful in two cases: for platforms that don't have such requirements and platforms for which we have no explicit support yet and that don't work well with the generic IR platform.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
This can be used to fix test failures on Windows when re-applying D98931
llvm/tools/lli/lli.cpp | ||
---|---|---|
242 | Inactive appeared to me as a sound term in code. Alternatives like No/None/Disabled/Passive seemed misleading in one or the other context (e.g. setUp__Platform). For the option value I am uncertain. On the one hand it's always good to keep terms aligned, on the other hand it might be confusing the user. It could also be Off or something else. What do you think? |
Comment Actions
Apply MCJIT small code-model tests to ORC in preparation for default JIT engine switch
Inactive appeared to me as a sound term in code. Alternatives like No/None/Disabled/Passive seemed misleading in one or the other context (e.g. setUp__Platform).
For the option value I am uncertain. On the one hand it's always good to keep terms aligned, on the other hand it might be confusing the user. It could also be Off or something else.
What do you think?