public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fxue at os dot amperecomputing.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/104377] New: Unreachable code in create_specialized_node of ipa-prop.c?
Date: Fri, 04 Feb 2022 06:48:36 +0000 [thread overview]
Message-ID: <bug-104377-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104377
Bug ID: 104377
Summary: Unreachable code in create_specialized_node of
ipa-prop.c?
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: fxue at os dot amperecomputing.com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
For function create_specialized_node(), the "node" to operated on seems always
to be an original cgraph node, never a clone node. From call graph related to
the function, we know that ipcp_decision_stage () only passes raw cgraph node
downwards to its callees. Then, "node" reaching create_specialized_node() would
not be a clone, so the code enclosed by "if (old_adjustments)" might be of no
use. But I am not sure sure if there is some thing that I missed.
ipcp_driver
|
'--> ipcp_decision_stage
|
'--> decide_whether_version_node
|
|--> decide_about_value
| |
'-----'--> create_specialized_node
next reply other threads:[~2022-02-04 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 6:48 fxue at os dot amperecomputing.com [this message]
2022-02-04 12:21 ` [Bug ipa/104377] " fxue at os dot amperecomputing.com
2022-02-09 18:25 ` jamborm at gcc dot gnu.org
2022-02-09 18:30 ` jamborm at gcc dot gnu.org
2022-02-15 3:43 ` fxue at os dot amperecomputing.com
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-104377-4@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).