From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C4161384D0E8; Sat, 19 Nov 2022 20:11:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C4161384D0E8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1668888700; bh=SRDfYGwhbyaRdp0kTbWrCKg6F0qpSHMRhUCiXuCl/5M=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ws2Ynswnr8HtSL+bnInUO+/T7WluJbJYP+YbJ3DQnqJ+sx/xJ3oVAKVs5ju3zAsXI 47iD7kIy2tZIvJwI7Ce/lZM2SewgGdoQyF+WWgUEw3LA7LrO+KeD5d8/5zbeEgdjyB hzZTLskC8nVyMsavIgqoudyKLCy7VcXzAE3Bf46M= From: "slyfox at gcc dot 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: Sat, 19 Nov 2022 20:11:39 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: blocker X-Bugzilla-Who: slyfox at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107661 --- Comment #11 from Sergei Trofimovich --- I think I found the bug: r13-3358-ge0403e95689af7 cgraph_edge_brings_all_agg_vals_for_node() accidentally changed behaviour of the predicate: - before the change: ipa-cp triggers when constrop contains all possible ed= ges aggregates (ok). - after the change: ipa-cp triggers when constrop contains a subset(!) of possible edges aggregates (bad, redirects invalid values sometimes). Thus substitution of do3()->do3.constprop() redirects to the wrong target. Sounds plausible?=