3 ms·
Unfortunately compiler authors can be remarkably unconcerned about codegen bugs. I'm still waiting for a longjmp bug in clang from over a decade ago to be fixe
by cperciva 3y ago
Unfortunately compiler authors can be remarkably unconcerned about codegen bugs. I'm still waiting for a longjmp bug in clang from over a decade ago to be fixed:https://github.com/llvm/llvm-project/issues/21557 https://github.com/llvm/llvm-project/issues/21557
- gavinhoward 3y agoOh. My. Goodness. That is sickening. I use Clang. I use longjmp(). I'm glad I'm going to rewrite all of my stuff into my own language with a custom compiler.
- JonChesterfield 3y agoThere are lots of compiler bugs. The further you stray from the common use cases the more likely you are to hit them. There are also an appreciable number of hardware bugs. Some of the complexity in compilers is working around those so that applications don't need to. Your own compiler, assuming it emits machine code and avoids documented and undocumented hardware bugs, can be error free.
- pasmafaute 3y agoBrilliant :) I also agree with JonChesterfield on this one: even home-brew compilers might have bugs! That's why I always write in HEX machine code!
- kentonv 3y agoI was going to complain about a GCC codegen bug open since 2007 but it looks like it finally got fixed in 2020! https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33799 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33799 Clang still has the same bug though, filed in 2012. https://bugs.llvm.org/show_bug.cgi?id=12286 https://bugs.llvm.org/show_bug.cgi?id=12286
- armchairhacker 3y agoAt least they didn't turn it into a language feature https://stackoverflow.com/questions/18808226/why-is-typeof-null-object https://stackoverflow.com/questions/18808226/why-is-typeof-n... https://softwareengineering.stackexchange.com/a/336857 https://softwareengineering.stackexchange.com/a/336857