summaryrefslogtreecommitdiff
path: root/src/jit/ClrJit.exports
diff options
context:
space:
mode:
authorPat Gavlin <pagavlin@microsoft.com>2016-02-23 13:53:32 -0800
committerPat Gavlin <pagavlin@microsoft.com>2016-02-23 13:53:32 -0800
commitdfd6ab2348b4b151bb90d3bd7deb6a7304bbafac (patch)
treea81d30ebff326ea01fbe81d8b760f7c7e94b2d6c /src/jit/ClrJit.exports
parent1ef30f932c1092ead58f7923f6dda999ae77780a (diff)
downloadcoreclr-dfd6ab2348b4b151bb90d3bd7deb6a7304bbafac.tar.gz
coreclr-dfd6ab2348b4b151bb90d3bd7deb6a7304bbafac.tar.bz2
coreclr-dfd6ab2348b4b151bb90d3bd7deb6a7304bbafac.zip
Expose a hosting interface for the JIT.
This is the first significant step towards removing the JIT's dependence on utilcode. This change introduces a new interface, `ICorJitHost`, that allows functionality that would usually be provided by the OS to be overridden by the program that is hosting the JIT. At the moment, this is limited to memory allocation and configuration value (e.g. environment variable) access. If the JIT exports a function named `jitStartup`, an instance of the `ICorJitHost` must be provided via that function before the first call to `getJit`. The VM and other implementors of the JIT interface have been updated accordingly. Most implementors should use the common implementation of `ICorJitHost` (cleverly named `JitHost`) in utilcode which respects the CLR's hosting policy. Note that this change does not update RyuJIT (or any other JITs) to use any of the functionality exposed by `ICorJitHost`; that work is left for future changes. [tfs-changeset: 1578176]
Diffstat (limited to 'src/jit/ClrJit.exports')
-rw-r--r--src/jit/ClrJit.exports1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/jit/ClrJit.exports b/src/jit/ClrJit.exports
index 9a914d7038..0126e63b4d 100644
--- a/src/jit/ClrJit.exports
+++ b/src/jit/ClrJit.exports
@@ -1,2 +1,3 @@
getJit
+jitStartup
sxsJitStartup