public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/89494] Bootstrap error when using GCC 4.2.1 Date: Wed, 15 Apr 2020 13:17:00 +0000 [thread overview] Message-ID: <bug-89494-4-lGYmvO5nC2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89494-4@http.gcc.gnu.org/bugzilla/> 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 <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:c00568f376078129196740d83946d54dc5437401 commit r10-7736-gc00568f376078129196740d83946d54dc5437401 Author: Gustavo Romero <gromero@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 <gromero@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.
next prev parent reply other threads:[~2020-04-15 13:17 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89494-4@http.gcc.gnu.org/bugzilla/> 2020-04-11 3:15 ` pkubaj at anongoth dot pl 2020-04-11 18:02 ` pkubaj at anongoth dot pl 2020-04-11 18:08 ` pkubaj at anongoth dot pl 2020-04-12 11:18 ` pkubaj at anongoth dot pl 2020-04-12 15:54 ` pkubaj at anongoth dot pl 2020-04-14 20:36 ` jakub at gcc dot gnu.org 2020-04-14 21:08 ` iains at gcc dot gnu.org 2020-04-14 21:13 ` jakub at gcc dot gnu.org 2020-04-15 12:20 ` jakub at gcc dot gnu.org 2020-04-15 13:17 ` cvs-commit at gcc dot gnu.org [this message] 2020-04-15 13:42 ` pkubaj at anongoth dot pl 2020-04-15 14:46 ` jakub at gcc dot gnu.org 2020-04-16 8:16 ` cvs-commit at gcc dot gnu.org 2020-05-01 1:36 ` pkubaj at anongoth dot pl 2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org 2021-03-24 20:03 ` iains at gcc dot gnu.org 2021-03-24 20:55 ` pkubaj at anongoth dot pl 2021-03-24 21:12 ` iains at gcc dot gnu.org 2021-04-10 17:03 ` pkubaj at anongoth dot pl 2024-03-17 4:18 ` iains at gcc dot gnu.org 2024-03-17 10:45 ` pkubaj at anongoth dot pl 2024-03-17 19:00 ` pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-89494-4-lGYmvO5nC2@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).