1.8 KiB
title, type, source, source_url, author, handle, post_id, date, archived, draft, tags, description, in_reply_to
| title | type | source | source_url | author | handle | post_id | date | archived | draft | tags | description | in_reply_to | |||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-width-height log file with an atomic for multi-thread|process messages - but even that seems too complexy ... | archive | https://x.com/NOTimothyLottes/status/2061123768429211767 | NOTimothyLottes | NOTimothyLottes | 2061123768429211767 | 2026-05-31 | 2026-08-23 | false |
|
no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-width-height log file with an atomic for multi-thread|process messages - but even that seems too complexy ... |
Source
- URL: https://x.com/NOTimothyLottes/status/2061123768429211767
- Author: NOTimothyLottes (@NOTimothyLottes)
- Posted: 2026-05-31 16:32:54
Thread
1/ @NOTimothyLottes ^2061123768429211767
no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-width-height log file with an atomic for multi-thread|process messages - but even that seems too complexy ...
2/ @NOTimothyLottes ^2061124536729207080
moving to this >>> CART file is mmapped on CPU with mapped GPU access (no file IO) - background page walker to ensure OS won't page it out - beginning of CART file is a grid of 32-bit unsigned values - hex dumping that as my 'log file' - either to term or GPU render
3/ @NOTimothyLottes ^2061124942968545433
hits the easy to debug CPU or GPU stuff in the same framework (simply write and it just appears) - it's always a HEX dump, but can show decimal by pretending it's a 4-bit/character terminal with a hex font :)