https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99117
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Pedantically speaking if __e in the end reads _M_data of some std::valarray that happens to alias __p it will be still violating aliasing, but at least current GCC won't do anything with that.
