Commit Graph
2 Commits
Author SHA1 Message Date
BlackMarkandClaude Opus 5.5 f8e136e8ad docs: comments state what is, not how it came to be
The loader build, the gate script and the line-ending rule each carried the
story of their arrival - a measurement off the bench, a loop got wrong by
hand, a checkout reached from two hosts - where a sentence of what holds now
is enough. .gitattributes loses two patterns for files this repository does
not have, .clangd its two non-ASCII dashes, two headers a "per C" that read
as a stripped degree sign, and the README a "(new)" and the port's own
first attempt at stopping monitor.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-23 21:50:31 +02:00
BlackMarkandClaude Fable 5 1489f4c3a0 editor: clangd and cmake work from a committed vscode workspace
The three files libavr's consumers carry, in the leaf-application shape:
nothing vendors this repo, so .clangd names the one build tree an editor
should read (build/atmega328p-generated) beside the stand-ins clang needs
for GCC's AVR dialect; .vscode/settings.json passes --query-driver and names
the toolchain prefix for the window that opens this folder. The libavr pin
advances to the editor-audit fixes. One residue stays red and is the
documented frontend divergence, not a defect: thermistor.hpp's consteval
Beta-equation table folds __builtin_log under GCC, which clang refuses to
fold in a constant expression -- the same class as libavr's breathe example
and its __builtin_cos.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-09 16:48:46 +02:00