Tag: #jit

한국어English日本語中文

← All posts

• ZJIT's Lightweight Frames — How Ruby 4.1 Erases Method-Frame Pushes, and What It Costs

  Ruby 4.0 shipped ZJIT on December 25, 2025 — but shipped it turned off: it's compiled into the binary, yet the default JIT is still YJIT. The official release notes put it this way: "ZJIT is faster than the interpreter,

  2026-07-16 · 20 min read #ruby#zjit#yjit#jit#compiler

• .NET 11 Runtime-Async: A Progress Report on Moving the Async State Machine from Compiler to Runtime

  C's async/await has been purely a compiler feature since 2012 — Roslyn rewrites the method body into a state-machine class, and the runtime executes it without ever knowing it was async. .NET 11's runtime-async moves tha

  2026-07-16 · 18 min read #dotnet#csharp#async#jit#performance

• Modern Python in 2026 — Python 3.13 / 3.14 / free-threaded / uv / Ruff / Polars 1.0 / FastAPI / Litestar / Robyn deep-dive

  In 2026 Python is the first time in 30 years that the language has crossed two huge inflection points at once. The first is the language itself — Python 3.13 brought the free-threaded preview and the JIT preview, and 3.1

  2026-05-16 · 29 min read #python#python-3-13#python-3-14#free-threaded#jit

• CPython Bytecode Interpreter Deep Dive — ceval.c, Specializing Adaptive, PEP 659, Copy-and-Patch JIT (2025)

  Python is slow, but most developers do not actually know why, or how it is getting faster. This post dissects CPython's heart, the ceval.c interpreter, from scratch: source to AST to bytecode, Code/Frame/Cell objects, th

  2026-04-15 · 16 min read #python#cpython#bytecode#interpreter#jit

• Compilers and Modern Language Runtimes — LLVM, JIT, GC, V8 TurboFan/Maglev, Inline Caching, Escape Analysis, Rust Monomorphization Complete Guide (2025)

  Everything that happens from a line of code to CPU execution. LLVM's dominance, V8's 4-tier JIT, Hidden Classes and Inline Caching, Escape Analysis, GC lineage from Mark & Sweep to ZGC, Go's work-stealing scheduler, Rust

  2026-04-15 · 11 min read #compiler#runtime#llvm#jit#garbage-collection

• Compilers and Interpreters: How Code Actually Runs — Everything Developers Need to Know

  A complete deep-dive into how code executes! Lexing → Parsing → AST → IR → Code Generation, Compiler vs Interpreter vs JIT, V8 (JS), CPython (Python), JVM (Java), GCC/LLVM, GraalVM — build the performance intuition every

  2026-03-23 · 17 min read #compiler#interpreter#lexer#parser#ast