https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80641
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> --- So based my findings around c#5 we can classify this as a false positive. GCC has enough information lying around to prove the problematical memset can never be reached, but fails to do so. Martin's patch to drop some annotations into our std::vector implementation is being discussed on the libstdc++ list. I think if/when that patch goes forward we reduce this to a non-regression misssed optimization -- and we'll probably need to include cpp output for the testcase so that it's note tainted in the future with Martin's annotations.