@iralmeida@mastodon.gamedev.place
Post #2285595
2025-11-27 19:46 UTC
@rovarma@mastodon.gamedev.place I spent the day revisiting how computers work, it was too fuzzy! 🙈
Thankfully I got @brendangregg 's Systems Performance book to the rescue (thx!) plus some intel processor manual. so now I got +1 wisdom for stack frames and traces 🥳
But I got to say, I find it really complicated regarding differences between architectures and the frame pointer being optional and the different methods for stack walking.
Replies (1)
-
@iralmeida@mastodon.gamedev.place 2025-11-27 19:53
@rovarma@mastodon.gamedev.place I didn't get into DWARF and never worked with C++ exceptions, so I haven't put much thought to the runtime machinery it needs. 🤷♀️ That said, I tried reading the article again. And success! There is no need to understand a stack frame and why the bytecode is like that, since you give it as a given that Superluminal's sampling relies on the data as is. It's about doing it faster, not different and the optz story and thought process are super nice to follow!