From: Martin Jambor <mjambor@suse.cz>
To: Jan Hubicka <hubicka@kam.mff.cuni.cz>
Cc: gcc@gcc.gnu.org
Subject: Re: distinguishing gcc compilation valgrind false positives
Date: Thu, 25 Nov 2021 11:08:41 +0100 [thread overview]
Message-ID: <ri68rxcim3a.fsf@suse.cz> (raw)
In-Reply-To: <20211124194556.GA13308@kam.mff.cuni.cz>
Hi,
On Wed, Nov 24 2021, Jan Hubicka via Gcc wrote:
>> ==5404== Conditional jump or move depends on uninitialised value(s)
>> ==5404== at 0x25DAAD7: incorporate_penalties (ipa-cp.c:3282)
>> ==5404== by 0x25DAAD7: good_cloning_opportunity_p(cgraph_node*, sreal,
>> sreal, profile_count, int) (ipa-cp.c:3340)
>
> I looked at this one (since it is in code I am familiar with) and I
> think it may be real bug. There are flags node_is_self_scc which does
> not seem to be initialized in the constructor.
>
> diff --git a/gcc/ipa-prop.h b/gcc/ipa-prop.h
> index 42842d9466a..1d0c115465c 100644
> --- a/gcc/ipa-prop.h
> +++ b/gcc/ipa-prop.h
> @@ -623,8 +623,8 @@ ipa_node_params::ipa_node_params ()
> : descriptors (NULL), lattices (NULL), ipcp_orig_node (NULL),
> known_csts (vNULL), known_contexts (vNULL), analysis_done (0),
> node_enqueued (0), do_clone_for_all_contexts (0), is_all_contexts_clone (0),
> - node_dead (0), node_within_scc (0), node_calling_single_call (0),
> - versionable (0)
> + node_dead (0), node_within_scc (0), node_is_self_scc (0),
> + node_calling_single_call (0), versionable (0)
> {
> }
Oops, can you please commit the change to master and all active
branches?
Thanks,
Martin
next prev parent reply other threads:[~2021-11-25 10:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 19:05 Zdenek Sojka
2021-11-24 19:15 ` Paul Floyd
2021-11-24 19:31 ` Zdenek Sojka
2021-11-24 20:02 ` Paul Floyd
2021-11-24 19:31 ` Jeff Law
2021-11-24 19:38 ` Jakub Jelinek
2021-11-24 19:41 ` Zdenek Sojka
2021-11-24 23:12 ` Jeff Law
2021-11-24 19:45 ` Jan Hubicka
2021-11-25 10:08 ` Martin Jambor [this message]
2021-11-25 10:12 ` Jan Hubicka
2021-11-25 11:49 ` Zdenek Sojka
2021-11-25 11:53 ` Jan Hubicka
2021-11-25 12:00 ` Zdenek Sojka
2021-11-25 13:50 ` Martin Liška
2021-11-24 21:30 ` Thomas Schwinge
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=ri68rxcim3a.fsf@suse.cz \
--to=mjambor@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@kam.mff.cuni.cz \
/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).