https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120850
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #11 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
Invalid as GCC *cannot* optimize memset_explicit away as long as it does not
know the semantics of memset_explicit at all.
If it's optimized away we'd have a severe bug: the functions creating a file,
printing something onto the console, etc. would also be optimized away and the
bug would have to be fixed in general, not by special casing memset_explicit.
