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 tree-optimization/40635] [12/13 Regression] bogus name and location in 'may be used uninitialized' warning
Date: Mon, 05 Dec 2022 15:51:10 +0000 [thread overview]
Message-ID: <bug-40635-4-39DlGPvD6v@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-40635-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40635
--- Comment #27 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:0d14720f93a8139a7f234b2762c361e8e5da99cc
commit r13-4495-g0d14720f93a8139a7f234b2762c361e8e5da99cc
Author: Richard Biener <rguenther@suse.de>
Date: Mon Dec 5 16:03:21 2022 +0100
middle-end/40635 - SSA update losing PHI arg loations
The following fixes an issue where SSA update loses PHI argument
locations when updating PHI nodes it didn't create as part of the
SSA update. For the case where the reaching def is the same as
the current argument opt to do nothing and for the case where the
PHI argument already has a location keep that (that's an indication
the PHI node wasn't created as part of the update SSA process).
PR middle-end/40635
* tree-into-ssa.cc (rewrite_update_phi_arguments): Only
update the argument when the reaching definition is different
from the current argument. Keep an existing argument
location.
* gcc.dg/uninit-pr40635.c: New testcase.
next prev parent reply other threads:[~2022-12-05 15:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-40635-4@http.gcc.gnu.org/bugzilla/>
2013-11-01 21:56 ` [Bug tree-optimization/40635] " manu at gcc dot gnu.org
2013-12-19 10:17 ` manu at gcc dot gnu.org
2013-12-19 10:40 ` philipp at marek dot priv.at
2013-12-19 10:51 ` manu at gcc dot gnu.org
2013-12-19 10:57 ` philipp at marek dot priv.at
2013-12-19 10:59 ` philipp at marek dot priv.at
2021-03-25 21:07 ` msebor at gcc dot gnu.org
2021-03-25 21:08 ` msebor at gcc dot gnu.org
2021-03-25 22:40 ` msebor at gcc dot gnu.org
2021-12-15 18:43 ` msebor at gcc dot gnu.org
2021-12-15 18:48 ` [Bug tree-optimization/40635] [12 Regression] " msebor at gcc dot gnu.org
2021-12-15 19:00 ` msebor at gcc dot gnu.org
2021-12-15 19:14 ` pinskia at gcc dot gnu.org
2021-12-18 10:46 ` pinskia at gcc dot gnu.org
2022-01-21 13:56 ` rguenth at gcc dot gnu.org
2022-03-17 19:25 ` msebor at gcc dot gnu.org
2022-03-17 22:00 ` pinskia at gcc dot gnu.org
2022-05-06 8:29 ` [Bug tree-optimization/40635] [12/13 " jakub at gcc dot gnu.org
2022-11-20 3:11 ` law at gcc dot gnu.org
2022-12-05 15:00 ` rguenth at gcc dot gnu.org
2022-12-05 15:51 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-08 12:21 ` [Bug tree-optimization/40635] [12 " rguenth 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-40635-4-39DlGPvD6v@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).