3 ms·
Initial, yes, but this was first uncovered in Oct 2015. That seems like long enough to fix it.
by galangalalgol 6y ago
Initial, yes, but this was first uncovered in Oct 2015. That seems like long enough to fix it.
- masklinn 6y agoIt’s not a single bug, it’s a bunch of different bugs in the interactions between noalias and various analysis and optimisation passes.
- saagarjha 6y agoAliasing analysis is a complicated part of the compiler, and it underpins a lot of optimization passes. It’s not an easy thing to bolt on.
- masklinn 6y agoTBF the internal API could be designed more pessimistically, as in llvm could drop noalias annotations unless they’re explicitly maintained (/ converted). This means optimisation phases would need to explicitly opt-in and aliasing optimisations would commonly be missed by default, but it would avoid miscompilations.