https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86714
--- Comment #2 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- You must have overlooked this response from Jakub: https://gcc.gnu.org/ml/gcc-patches/2018-07/msg01238.html "If we just warn about the initializer and treat it some way, an optimization should not change how the initializer is treated. The memcpy and memset themselves must be valid and they should just copy whatever is in the initializer without optimizations."
