https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68034
--- Comment #6 from Joseph S. Myers <jsm28 at gcc dot gnu.org> --- It's not clear that the compiler not knowing anything about memset_explicit is optimal either. We don't want the compiler to *optimize out* calls to memset_explicit. But there's the case where the sensitive data is entirely in local variables that might never appear be written to memory at all in the absence of a call to memset_explicit, where the use of memset_explicit *causes* the undesired write to memory in the first place so that the data can be overwritten in memory (not knowing about memset_explicit means not knowing that it doesn't actually care about what data is in the pointed-to memory).
