When I was a newbie, I would often say things like "maybe the compiler is broken" or "maybe the cpu is doing it wrong."
Of course, it was never the tools. it was always me.
Years later, of course, I work on unreleased hardware. And yeah, sometimes it's broken. It's really fucking odd. Write C code, and holy shit, it's actually a compiler bug or CPU bug.
Life was simpler when I was just ignorant and egotistical. Now I'm... well, still ignorant and egotistical, I guess, but often deal with actual hardware bugs.
Finding an assembler bug is also interesting. Marched up against a nasm bug once that kept me debugging for quite a while. The good thing with assembler bugs, however, is that you can decompile the generated machine code to something that is really close to your original source code... That helped a lot.
Of course, it was never the tools. it was always me.
Years later, of course, I work on unreleased hardware. And yeah, sometimes it's broken. It's really fucking odd. Write C code, and holy shit, it's actually a compiler bug or CPU bug.
Life was simpler when I was just ignorant and egotistical. Now I'm... well, still ignorant and egotistical, I guess, but often deal with actual hardware bugs.