World Age for beginners: one way to compile a dynamic language - Internals & Design - Julia Programming Language

https://discourse.julialang.org/t/world-age-for-beginners-one-way-to-compile-a-dynamic-language/134402/

Very cool article explaining how Julia’s world age — the counter of the global state — works so that the compiler gets more information to optimise even if there is an `eval` in the function body.

#Julia #Compiler #JIT #JAOT

🤔 Ah, the riveting saga of the #GDB #JIT interface, where we discover that #debugging JIT-compiled code is as clear as mud without #DWARF sprinkles. 🐢 Because who wouldn't want to step through machine code one agonizing instruction at a time while GDB plays the clueless sidekick? 🤷‍♂️🔧
https://bernsteinbear.com/blog/gdb-jit/ #JITCompilation #DebuggingChallenges #CodingSaga #HackerNews #ngated
The GDB JIT interface

GDB is great for stepping through machine code to figure out what is going on. It uses debug information under the hood to present you with a tidy backtrace and also determine how much machine code to print when you type disassemble.

Max Bernstein
The GDB JIT interface

GDB is great for stepping through machine code to figure out what is going on. It uses debug information under the hood to present you with a tidy backtrace and also determine how much machine code to print when you type disassemble.

Max Bernstein

. This iterative approach lets you learn and pivot without risking the whole business. It’s a series of small, controlled experiments.

Applying Toyoda’s Just-In-Time principle turns your supply chain from a rigid liability into a flexible asset. It lets you respond to what your customers are actually buying right now.

#JustInTime #JIT #Agile #SupplyChainManagement #RetailManagement #HardwareRetail #Toyota #LeanManufacturing #InventoryManagement #BusinessAgility (8/8)

Published my first PyPI package today, called lafleur.

#lafleur is a specialized CPython JIT fuzzer that uses a coverage-guided, evolutionary approach. It executes test cases, observes their effect on the JIT's state by analyzing verbose trace logs, and uses that feedback to guide its mutations, becoming smarter at finding interesting code paths over time.

Let me know if you use it or have any questions.

https://pypi.org/project/lafleur/
https://github.com/devdanzin/lafleur

#Python #CPython #fuzzer #fuzzing #JIT

Client Challenge

"Een weekje sneeuw legt de kwetsbaarheden van Nederland bloot"

-> "We hebben Nederland „ontzettend efficiënt en goedkoop ingericht”, zegt Annelies van Vark, die zich op Instituut Clingendael specialiseerde in weerbaarheid"

-> " „Vaak wordt gezegd: just in time and just enough. In goede tijden kom je daarmee weg. Maar als een klein dingetje misgaat, loopt alles in de soep.” "

(Via @nrc_nl ) #Nederland #sneeuw #JiT
https://www.nrc.nl/nieuws/2026/01/09/een-weekje-sneeuw-legt-de-kwetsbaarheden-van-nederland-bloot-a4917220

Een weekje sneeuw legt de kwetsbaarheden van Nederland bloot

Weerbaarheid: Na corona werd besloten dat Nederland beter voorbereid moet zijn op grootschalige ontwrichtingen. Een paar dagen sneeuw bewijzen dat dit nog niet opschiet.

NRC

Some new preliminary numbers from Ken Jin for the JIT in Python 3.15:

"On AArch64 macOS, the JIT has a 7-8% speedup over the tail calling interpreter with all optimizations enabled."

https://docs.python.org/3.15/whatsnew/3.15.html#whatsnew315-jit

https://github.com/python/cpython/commit/d9c1235db44100b16355a347ca9e304df48411a7

This is in addition to 3-4% over the standard CPython interpreter on x86-64 Linux.

See also https://doesjitgobrrr.com

#Python #Python315 #JIT #CPython

The GDB JIT interface
Max Bernstein
https://bernsteinbear.com/blog/gdb-jit/

#GDB #debug #JIT

The GDB JIT interface

GDB is great for stepping through machine code to figure out what is going on. It uses debug information under the hood to present you with a tidy backtrace and also determine how much machine code to print when you type disassemble.

Max Bernstein

Disabling #JIT compilation on #PostgreSQL has been a revelation. One of my queries (against my closure table for threading) went from 4 seconds to about 100ms. And that query gets hit a lot because it's loaded opportunistically as I scroll in the UI.

It made a huge difference there but also just in general because my queries tend to be non-trivial and the system was making the wrong choice to invoke the JIT often.

Enigmatick

ZJIT is now available in Ruby 4.0

ZJIT is now available with the release of Ruby 4.0. Here’s an update of our progress.

Rails at Scale