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 middle-end/101292] [12 Regression] recent valgrind error in warning-control.cc since r12-1804-g65870e75616ee4359d1c13b99be794e6a577bc65
Date: Mon, 17 Jan 2022 15:17:03 +0000 [thread overview]
Message-ID: <bug-101292-4-Z7rFepbQ8y@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101292-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101292
--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:1374d4b963a6ac2e0ec1645c09e5162e68b009d6
commit r12-6640-g1374d4b963a6ac2e0ec1645c09e5162e68b009d6
Author: Richard Biener <rguenther@suse.de>
Date: Mon Jan 17 15:22:11 2022 +0100
middle-end/101292 - invalid memory access with warning control
The warning control falls into the C++ trap of using a reference
to old hashtable contents for a put operation which can end up
re-allocating that before reading from the old freed referenced to
source. Fixed by introducing a temporary.
2022-01-17 Richard Biener <rguenther@suse.de>
PR middle-end/101292
* diagnostic-spec.c (copy_warning): Make sure to not
reference old hashtable content on possible resize.
* warning-control.cc (copy_warning): Likewise.
next prev parent reply other threads:[~2022-01-17 15:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 7:59 [Bug c/101292] New: recent valgrind error in warning-control.cc dcb314 at hotmail dot com
2021-07-02 8:19 ` [Bug c/101292] " marxin at gcc dot gnu.org
2021-07-02 8:23 ` [Bug middle-end/101292] [12 Regression] " rguenth at gcc dot gnu.org
2021-07-02 9:05 ` marxin at gcc dot gnu.org
2021-07-02 9:21 ` [Bug middle-end/101292] [12 Regression] recent valgrind error in warning-control.cc since r12-1804-g65870e75616ee4359d1c13b99be794e6a577bc65 marxin at gcc dot gnu.org
2021-07-02 14:57 ` msebor at gcc dot gnu.org
2021-10-15 6:52 ` dcb314 at hotmail dot com
2022-01-17 14:23 ` rguenth at gcc dot gnu.org
2022-01-17 15:17 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-17 15:18 ` rguenth at gcc dot gnu.org
2022-01-17 18:21 ` tschwinge at gcc dot gnu.org
2022-01-18 10:38 ` rguenther at suse dot de
2022-01-18 11:33 ` dcb314 at hotmail dot com
2022-01-18 11:50 ` rguenther at suse dot de
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-101292-4-Z7rFepbQ8y@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: link
Be 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).