Top all-time · #14157
The Infinite Loop
Personal blog · geidav.wordpress.comprogramminggames
The Infinite Loop is a personal blog at geidav.wordpress.com about programming and games. Since 2013, 5 different Hacker News readers have linked it 5 times. The last post was in 2017, but the archive is still widely read.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
Linked for a making-of post on a 64k demoscene intro and for a stack-probing tag, cited on Windows stack guard pages. Commenters cite the posts as examples or references, not as praise.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Tales from a lean programmer.
Most-linked posts?
- /tag/stack-probing/2 people · 2 mentions · first linked 2018-02-14
What Hacker News says?
It's 12 years old now, but I am still extremely impressed by this 64k intro https://geidav.wordpress.com/2013/04/14/making-of-turtles-al... and also by this 4k intro https://www.youtube.com/watch?v=_YWMGuh15nE :) And overall this website is extremely interesting with tutorials and code and great explanations https://iquilezles.org/
Comment linking /2013/04/14/making-of-turtles-all-the-way-down
on “The demoscene as a UNESCO heritage in Sweden”Submitted An overview of direct memory access (2014) as a story · 64 points
HN discussionLet's be clear on the difference between C and C++ undefined behaviour, and machine behaviour that GCs and runtimes can use for implementation. It is not unusual to rely on triggering a hardware exception in runtimes and GCs, up to and including segfaults. For example, a check for safepoint might be implemented by attempting to read a particular address. When the GC needs to stop the world, it could change the prote…
Comment linking /tag/stack-probing/
on “LLVM’s garbage collection facilities and SBCL’s generational GC”Submitted The Making of “Turtles all the way down” as a story · 54 points
HN discussionwhich results in the stack pointer moving outside of the bounds of the currently mapped stack region, jumping over the stack guard pages. They don't generate stack probes? I'm used to this behaviour on Windows, where the compiler will generate code to explicitly touch the guard pages if it knows/suspects you may allocate more than a page: https://geidav.wordpress.com/tag/stack-probing/ Yes, I know if you try to get…
Comment linking /tag/stack-probing/
on “Systemd (PID1) crash with specially crafted D-Bus message”