#cpp

Wiki 5

  • A Simplified Model of Fil-C Walks through how Fil-C makes C/C++ memory-safe โ€” shadow AllocationRecord pointers, parallel "invisible bytes" for heap pointers, and a GC
  • How do I deal with memory leaks? Stroustrup's C++ FAQ answer โ€” write code without leaks by hiding allocation in containers and resource handles, not by chasing leaks after the fact
  • Pointer Provenance The idea that a pointer carries not just an address but an identity tied to the allocation it was derived from, which compilers must respect
  • RAII Resource Acquisition Is Initialization โ€” bind resource lifetime to object lifetime so cleanup runs deterministically when the object goes out of scope
  • Shared memory consistency from scratch, part 1: causality Alloth designs a deliberately permissive multiprocessor to derive memory-model rules, and argues the C++11/20 atomics model gets causality wrong

Toolbox 6

  • Fil-C Memory-safe C/C++ compiler giving every pointer a bounds-checked capability and a GC, no rewrites
  • Free Ink Open e-reader stack โ€” CrossPoint firmware for Xteink devices, a hardware-independent e-paper firmware SDK, and de-link, a $60 hand-solderable ESP32-S3 reader board
  • gap Native side-by-side GUI diff viewer built as a testbed for linear-space Myers diff
  • ik_llama.cpp ikawrakow's llama.cpp fork with IQK quants, Q6 KV cache and faster long-context prompt processing
  • llama.cpp C/C++ inference engine for GGUF open-weights models, the base most local-LLM tools wrap
  • pvz-ps2 Plants vs. Zombies on PlayStation 2 โ€” a GL subset over gsKit bolted onto the PvZ decompilation