https://www.memcp.org/index.php?action=history&feed=atom&title=JIT_CompilationJIT Compilation - Revision history2026-08-29T08:27:43ZRevision history for this page on the wikiMediaWiki 1.39.1https://www.memcp.org/index.php?title=JIT_Compilation&diff=301&oldid=prevWikiservice: Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference2026-08-28T09:59:18Z<p>Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference</p>
<p><b>New page</b></p><div><!-- Copyright (C) 2026 Carl-Philip Haensch --><br />
<!-- SPDX-License-Identifier: GPL-3.0-or-later --><br />
<br />
<span id="jit-compilation"></span><br />
= JIT Compilation =<br />
<br />
<!-- Generated from MemCP c42e19eba on 2026-08-27; do not edit manually. --><br />
<div class="mw-message-box mw-message-box-notice">Generated from MemCP commit <code>c42e19eba</code> on 27 August 2026. See [[Full SCM API documentation]].</div><br />
<br />
The '''JIT Compilation''' module requests and inspects native compilation of supported Scheme procedures. JIT availability depends on the build and architecture; the current native emitter targets x86-64.<br />
<br />
Compilation is an optimization, not a semantic mode. Unsupported procedures remain interpreted, and diagnostic helpers can report unexpected fallback without changing the procedure's result.<br />
<br />
MemCP's performance roadmap extends native compilation from individual supported procedures toward complete shard-local scan loops: storage decoders provide known value types, filter/map/reduce expressions become one tight loop, and vectorized batches amortize callback overhead. Additional architecture backends remain planned rather than current support.<br />
<br />
JIT coverage is an active performance boundary. Real application workloads can currently lose to MySQL when important operators remain interpreted or compilation cost dominates a short query. The goal is broader native coverage without weakening garbage-collector safety, cancellation, pointer lifetime or interpreter-equivalent results.<br />
<br />
== jit ==<br />
<br />
compiles a lambda to optimized native code when this build enables JIT<br />
<br />
'''Allowed number of parameters:''' 1–1<br />
<br />
<span id="parameters"></span><br />
=== Parameters ===<br />
<br />
* '''fn''' (<code>any</code>): the function to compile<br />
<br />
<span id="returns"></span><br />
=== Returns ===<br />
<br />
* '''value''' (<code>any</code>)<br />
<br />
<span id="jit-1"></span><br />
== jit? ==<br />
<br />
tells whether a value is a JIT-compiled function descriptor<br />
<br />
'''Allowed number of parameters:''' 1–1<br />
<br />
<span id="parameters-1"></span><br />
=== Parameters ===<br />
<br />
* '''value''' (<code>any</code>): value to inspect<br />
<br />
<span id="returns-1"></span><br />
=== Returns ===<br />
<br />
* '''value''' (<code>bool</code>)<br />
<br />
== jit-warn-if-fallback ==<br />
<br />
prints a diagnostic warning when an enabled JIT build kept a procedure interpreted and returns the procedure unchanged<br />
<br />
'''Allowed number of parameters:''' 1–2<br />
<br />
<span id="parameters-2"></span><br />
=== Parameters ===<br />
<br />
* '''procedure''' (<code>any</code>): procedure expected to be a native compilation candidate<br />
* '''label''' (<code>string</code>): optional diagnostic label ''(optional)''<br />
<br />
<span id="returns-2"></span><br />
=== Returns ===<br />
<br />
* '''value''' (<code>any</code>)<br />
<br />
<span id="jit-enabled"></span><br />
== jit-enabled? ==<br />
<br />
tells whether this binary was built with the patched Go JIT runtime<br />
<br />
'''Allowed number of parameters:''' 0–0<br />
<br />
<span id="parameters-3"></span><br />
=== Parameters ===<br />
<br />
''This function has no parameters.''<br />
<br />
<span id="returns-3"></span><br />
=== Returns ===<br />
<br />
* '''value''' (<code>bool</code>)</div>Wikiservice