Top all-time · #12048
miyuki's blog
Personal blog · miyuki.github.ioprogrammingsystems
miyuki's blog is a personal blog at miyuki.github.io about programming and systems. Since 2017, 6 different Hacker News readers have linked it 7 times, most often “Building and using a 29-year-old compiler on a modern system”. The last post was in 2017, but the archive is still widely read.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers cite these posts on low-level C and C++ topics: std::launder, byte order, C++ design, and archaeology of early GCC and building old GCC versions.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- Building and using a 29-year-old compiler on a modern system4 people · 4 mentions · first linked 2017-10-05
- std::launder: the most obscure new feature of C++17 (2016)3 people · 3 mentions · first linked 2021-05-09
What Hacker News says?
>C++ has added/will add std::launder and std::bless to deal with this issue You're thinking of std::bit_cast. std::launder solves a different, much more obscure problem: https://miyuki.github.io/2016/10/21/std-launder.html
Comment linking /2016/10/21/std-launder.html
on “The Byte Order Fiasco”Submitted Building and using a 29-year-old compiler on a modern system as a story · 139 points
HN discussionI feel like C++ is a bunch of long chains of solutions creating problems that require new solutions, that start from claiming that it can do things better than C. Problem 1: You might fail to initialize an object in memory correctly. Solution 1: Constructors. Problem 2: Now you cannot preallocate memory as in SLAB allocation since the constructor does an allocator call. Solution 2: Placement new Problem 3: Now the t…
Comment linking /2016/10/21/std-launder.html
on “In Defense of C++”Submitted std::launder: the most obscure new feature of C++17 (2016) as a story · 41 points
HN discussionYeah. Here's a GCC developer experimenting with a 31-year old GCC version on a modern system (the first one with x86 support): >It is amazing how well things work – the modern assembler, linker, and debugger handles the code generated by GCC 1.27 without any problems. https://kristerw.blogspot.com/2019/01/building-gcc-127.html And the write-up he based his experiments upon: https://miyuki.github.io/2017/10/04/gcc-ar…
Comment linking /2017/10/04/gcc-archaeology-1.html
on “IT professionals should work in a mainframe environment at some point (2015)”Submitted Building and using a 29-year-old compiler on a modern system (2017) as a story · 13 points
HN discussionlove software archaeology like this. there was another article where someone bootstrapped the very first version of gcc that had the i386 backend added to it, and it turns out there was a bug in the codegen. I'll try to find it... EDIT: Found in, infact there was a HN discussion about an article referencing the original article: https://miyuki.github.io/2017/10/04/gcc-archaeology-1.html https://news.ycombinator.com/…
Comment linking /2017/10/04/gcc-archaeology-1.html
on “Let's compile Quake like it's 1997”