Yes, I use Claude Code to help with writing this — a motor condition means I
can't type at length anymore, so this is how I get technical work out these
days. The content isn't guesswork though: it's backed by things I actually
ran and checked myself -
- Real crash traces (SIGSEGV, then a SIGABRT with `_tlv_bootstrap_error` in
the lldb backtrace once the descriptor was structurally recognized)
- A byte-for-byte comparison against clang's own `-S` output for the same
source, to get the actual TLV descriptor layout and access sequence right
- Three working test programs, including a 4-thread pthread test that
verifies genuine per-thread isolation (independent storage addresses,
correct independent counters under concurrent access) - not just "it
didn't crash"
- A clean run of TinyCC's own `make test` suite (73_arm64, 124_atomic_counter,
125_atomic_misc, 136_atomic_gcc_style, 138/139/140/152_arm64_*, btest,
memtest, dlltest, cross-test) - no regressions
- The real V compiler (vlang/v) self-build, which is what motivated this,
compiling and running correctly through this path afterward
Happy to walk through any part of it in more detail, or answer questions
about specific design choices (register save/restore around the TLV thunkcall,
the section/header-flag plumbing dyld needs, the minos bump, etc.).
Richard Wheeler
Sent with [Proton Mail](https://proton.me/mail/home) secure email.
_______________________________________________
Tinycc-devel mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
