https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119881
--- Comment #2 from Tamar Christina <tnfchris at gcc dot gnu.org> --- (In reply to Richard Biener from comment #1) > I wonder where this matters in practice and my usual stance is educating > users > about __restrict or #pragma GCC ivdep or OMP simd safelen is better than > possibly slowing down cases where we _do_ alias by a lot. Possibly only > handling the case where we _always_ prove independence would be possible, > aka storing the disambiguation result in a global and never going the vector > way again when the disambiguation failed once. I guess one problem is that most cases I've seen this in is for C++ codebases for which there still isn't a standard restrict keyword and doesn't seem like there's any real movement here: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3635.pdf https://cplusplus.github.io/EWG/ewg-active.html#72 https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n3988.pdf https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4150.pdf https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1296r0.pdf Which for people developing cross compiler sources is problematic.
