Cx Dev Log — 2026-05-07

JIT Backend: Cracking the Realness Code

Back-edge sealing, assert native lowering, and functional tests—sounds like just another day in the trenches. This week marks a pivotal moment in the Cx language devlog, focusing on JIT correctness and leaving the merge backlog behind for a more intriguing question. Can the JIT really run Cx programs as intended?

No-Panic Guarantee on Valid IR

With PR #101 (CX-50), we see the JIT backend promising not to panic on any IR that successfully passes validate_module. Closing unsafe paths is key here:

1. 
   Back-edge Sealing Panic was a thorn in the side as Cranelift panicked on loops targeting a previously sealed block, now resolved by deferring seal_all_blocks() until all instructions are emitted.


2. 
   Float Arithmetic on Integer Ops is no longer a surprise party for the wrong guests. F64 operations mistakenly handed off to integer ops like iadd are cut off with an UnsupportedConstruct.


3. 
   Float Comparison Guard ensures proper type-checking, verifying builder.func.dfg.value_type() before deploying icmp.

This patch also corrects three missing read_only fields in BlockParam, pushed by previous CX-40 changes. Ending with 197 successful tests and an augmented host_boundary.rs by 258 lines, this work guarantees not just correctness in theory but secure invocation in practice.

Assert and Assert_eq Lower Natively

CX-48 advances by letting assert and assert_eq cut out the middleman, lowering directly through IR and Cranelift. Enter IrTerminator::Trap—a new, no-nonsense terminator—causing unconditional aborts.

Here’s how:

• 
  assert(cond): Forms a two-branch CFG, branching on condition, trapping on fail.


• 
  assert_eq(a, b): Uses Compare(Eq) with a similar branch-and-trap pattern.

With Trap, execution stops dead on failure instead of rambling through with control transfers. This translates into +588 lines across six files and a total of 204 tests in that branch.

First JIT Parity Baseline

The CX-51 change introduces a differential harness meant to push all interpreter tests through the JIT. The result: 23 passing, 97 skipping unsupported constructs, and zero parity failures out of 120 fixtures.

Achieving zero parity failures is the holy grail of these tests. It shows alignment with the interpreter across board, even as many constructions aren't JIT-ready. As more capabilities light up, the JIT scoreboard—tracking 23 successful JIT fixtures—will evolve. Meanwhile, it eliminates the silent exit zero faux pas, ensuring failure codes aren't lost in the cracks.

Determinism Testing

Then there’s CX-49, bringing determinism testing into play with a dozen tests for re-compiling IrModule and checking for identical results. Testing covers simple to complex constructs, from ConstInt to multiple functions. A formal spec, docs/backend/cx_jit_determinism.md, backs this up.

Achieving JIT predictability per session may not sound groundbreaking, but it feels like securing a future where debugging doesn't dig into recurring non-determinism bugs, making life simpler down the line.

Branch Management at Scale

Not forgetting steady hands, CX-45 and CX-44 calmly steered through rebasing and cleaning six branches. Conflicts speckled across host_boundary.rs suggest a typical day, each branch passing through audits and tests, showing 196 to 201 tests per branch.

Managing this highlights the complexity of 12+ active branches, but submain's trajectory strongly suggests steady progress stands ahead of a main merge delay, now expanded by 16+ non-merge commits.

What's Next

As the task turns towards merging six, rebased human reviews into submain, closing multiple phases, strides should soon include integrations of today’s latest branches (CX-47, CX-48, CX-49, CX-51). The real roadblock’s the submain-to-main merge—looming large and risky if ignored much longer.

Method call lowering and when block support—as part of Phase 11—remain in waiting, cast aside while the JIT backend deserves undivided attention. Assertive lowering of assert and assert_eq is progress, yet, handfuls of runtime intrinsics—print, println, printn, read, and input—stay untamed.

With 23 out of 120 fixtures JIT-ready, the path's clear to closing even more as pending branches weave into the main. Onward to closing those gaps:

Follow the Cx language project:

• Website: cx-lang.com
  


• GitHub: github.com/COMMENTERTHE9/Cx_lang
  


• Dev.to: dev.to/commenterthe9
  


• Bluesky: thecomment.bsky.social
  


• Twitter/X: @commenterthe9
  

Originally published at https://cx-lang.com/blog/2026-05-07