... ask HISTORIANS???

New (short) blog post: sneaky git commits tavianator.com/2025/sneaky....

A brief history and (ab)use of __VA_OPT__: tavianator.com/2025/cpp_chu...

New blog post: parallel ./configure tavianator.com/2025/configu...

Still no sound from my laptop speakers, but at least I won't trigger a UAF anymore while I try to debug it: lore.kernel.org/linux-sound/...

I could reproduce the phenomenon with only 14 instructions on #Intel #GoldenCove, #RaptorCove, #RedwoodCove. It appears only with the 64b-immediate initialization of the 2nd (3rd) operand in the -1024<=imm32<=1023 range. On #LionCove... 1/2

New blog post: tavianator.com/2025/shlx.html

I wrote more details here: github.com/andreas-abel...

So it turns out that on arm64 macOS, if you send SIGSEGV manually (kill -SEGV <pid>), the kernel fills in siginfo->si_code as if it were a "real" SIGSEGV. So your handler can't easily distinguish between a "real" and a "fake" SIGSEGV

TIL my name

A while ago I implemented some code for dynamic signal handler (un)registration: github.com/tavianator/b... The idea is you can call sighook(SIGINT, ...) from multiple places and all the registered hooks will get called when a signal is received.

Does anyone have a good writeup of the behaviour of explicit prefetches on modern x86 uarches? In particular the cost of prefetching an invalid address (unmapped or even non-canonical).

Made a quick script to compare `perf stat` results: gist.github.com/tavianator/b...

Wrote up my experience finding (and fixing) a bug in Btrfs: tavianator.com/2024/btrfs_b...