https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89494
--- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <ja...@gcc.gnu.org>: https://gcc.gnu.org/g:c00568f376078129196740d83946d54dc5437401 commit r10-7736-gc00568f376078129196740d83946d54dc5437401 Author: Gustavo Romero <grom...@linux.ibm.com> Date: Wed Apr 15 15:14:45 2020 +0200 selftest: Work around GCC 4.2 PR33916 bug by optimizing the ctor [PR89494] GCC 4.2 due to PR33916 miscompiles temp_dump_context ctor, because it doesn't zero initialize the whole dump_context temporary on which it runs the static get method and during destruction of the temporary an uninitialized pointer is deleted. More recent GCC versions properly zero initialize it and ideally optimize away the construction/destruction of the temporary, as it isn't used for anything, but there is no reason to create the temporary, static member functions can be called without an associated object. 2020-04-15 Gustavo Romero <grom...@linux.ibm.com> PR bootstrap/89494 * dumpfile.c (selftest::temp_dump_context::temp_dump_context): Don't construct a dump_context temporary to call static method.
