News for hackers. Stuff that matters.
Re:Make LLVM Fast Again by compiler-guy on Monday May 11, 2020 @10:45AM (#23142671)
In optimized code, it is far more likely that one has a programming error in one's source code that an aggressive optimization revealed, rather than a bug in an industrial compiler. For example, an uninitialized variable that ends up sharing a memory location with some other variable whose life-time doesn't overlap in optimized mode rather than having its own memory location without optimization.

That one is caught be a warning, but there are thousands of possible errors that can be exposed this way.

Compilers have bugs all the time, but code in a write-test-debug-cycle typically has many more.

Re:Make LLVM Fast Again by ludamad on Monday May 11, 2020 @11:18PM (#23150261)
Which is why equally aggressive debug checks are important