public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/107661] [13 Regression] lambdas get merged incorrectly in tempaltes, cause llvm-12 miscompilation since r13-3358-ge0403e95689af7 Date: Mon, 21 Nov 2022 22:52:17 +0000 [thread overview] Message-ID: <bug-107661-4-Ma6GGgwtRF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107661-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107661 --- Comment #14 from Martin Jambor <jamborm at gcc dot gnu.org> --- (In reply to Sergei Trofimovich from comment #13) > It seems to have something to do with > push_agg_values_from_edge()/push_agg_values_for_index_from_edge() behaviour > of filtering self-recursive lattice values: > > if (interim && self_recursive_pass_through_p (cs, jfunc, index)) > { > interim->push_adjusted_values (src_idx, index, unit_delta, > res); > return; > } Spot on. > > Here we seem to ignore lattice values discovered on the edges and only copy > already encountered values. But we only populate 'interim' with values we > specialised the self-recursive call against: > > push_agg_values_from_edge (cs, dest_info, &edge_values, &existing); > > ('existing' variable is populated by values caller uses in one location). > > > The following hack seems to fix the test case for me but I suspect it just > breaks any self-recursive propagation: No, it does not. The self-recursive hack, I mean feature, is meant to be used when push_agg_values_from_edge is called from find_aggregate_values_for_callers_subset. At that point we can assume we would change both the caller and the callee. But when it is called from cgraph_edge_brings_all_agg_vals_for_node it is not the right thing to do because it potentially leads only to redirection to a different callee. Correctness-wise your patch is a valid fix. But it would disable to computation avoidance code in push_agg_values_from_edge and so I'll propose a patch adding a parameter to push_agg_values_from_edge and its helper signaling whether they can be optimistic about self-recursive edges. Thank you for reporting and a very nice test-case.
next prev parent reply other threads:[~2022-11-21 22:52 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-12 18:06 [Bug middle-end/107661] New: [13 Regression] lambdas get merged incorrectly in tempaltes, cause llvm-12 miscompilation slyfox at gcc dot gnu.org 2022-11-12 18:13 ` [Bug middle-end/107661] " pinskia at gcc dot gnu.org 2022-11-12 18:21 ` slyfox at gcc dot gnu.org 2022-11-12 20:16 ` slyfox at gcc dot gnu.org 2022-11-12 22:47 ` slyfox at gcc dot gnu.org 2022-11-13 14:23 ` [Bug middle-end/107661] [13 Regression] lambdas get merged incorrectly in tempaltes, cause llvm-12 miscompilation since r13-3358-ge0403e95689af7 slyfox at gcc dot gnu.org 2022-11-13 14:57 ` jamborm at gcc dot gnu.org 2022-11-14 13:55 ` rguenth at gcc dot gnu.org 2022-11-15 23:21 ` slyfox at gcc dot gnu.org 2022-11-18 8:42 ` slyfox at gcc dot gnu.org 2022-11-18 8:43 ` slyfox at gcc dot gnu.org 2022-11-18 8:54 ` slyfox at gcc dot gnu.org 2022-11-19 20:11 ` slyfox at gcc dot gnu.org 2022-11-19 20:29 ` slyfox at gcc dot gnu.org 2022-11-20 21:26 ` slyfox at gcc dot gnu.org 2022-11-21 22:52 ` jamborm at gcc dot gnu.org [this message] 2022-11-22 14:13 ` [Bug ipa/107661] " jamborm at gcc dot gnu.org 2022-11-22 17:30 ` cvs-commit at gcc dot gnu.org 2022-11-22 17:33 ` jamborm at gcc dot gnu.org 2022-11-24 22:46 ` slyfox 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-107661-4-Ma6GGgwtRF@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).