rfc:jit
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:jit [2019/02/13 09:07] – dmitry | rfc:jit [2019/02/22 12:08] – Compatibility with C compilers without GCC explicit global register variables extension dmitry | ||
---|---|---|---|
Line 402: | Line 402: | ||
===== State and compatibility ===== | ===== State and compatibility ===== | ||
- | Currently we support | + | Currently we only support |
- | We support | + | We support " |
+ | There is no any restriction on C compiler any more. LLVM build works fine. Anatol Belski is going to work on Windows | ||
- | ZTS support is not a big problem, but it should be implemented | + | ZTS support is doable and shouldn' |
- | LLVM and MSVC are not supported | + | Windows is not currently |
- | + | ||
- | Alternative way to support all platforms and C compilers is generating low-level VM (using the same JIT framework). This VM won't depend on C compiler extensions, and going to be comptible with JIT out of the box. As a side effect, interpretation should also became faster. This approach is used in JVM template VM, low level WebKit interpreter, | + | |
===== Open Issues ===== | ===== Open Issues ===== |
rfc/jit.txt · Last modified: 2020/08/01 23:41 by carusogabriel