3 ms·

No, it is very often a compiler bug. Just look at the gcc, clang or rustc tickets. e.g. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=open&no_redirec

by rurban 2y ago

No, it is very often a compiler bug. Just look at the gcc, clang or rustc tickets. e.g. https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=__open__&no_redirect=1&order=Importance&product=gcc&query_format=specific https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=__open__... It's massive, and several gcc versions have to be blacklisted. The clang restrict bug is still not fixed, it never worked. rustc was never memory-, type- nor concurrency-safe.

cillian64 2y ago
Compared to the amount of code that people compile and the number of bugs seen and fixed in that code, that is a tiny number of bugs. I wouldn't say it's "never" a compiler error but when you find a bug in your program, it's almost certainly not the compiler's fault.