From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 4A8363858C52; Wed, 21 Sep 2022 06:55:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 4A8363858C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663743321; bh=t/16OToy+LHuLTHAvZOLLz5LZnlGjwsYIlp6aTIkmko=; h=From:To:Subject:Date:In-Reply-To:References:From; b=C4c+2ea9tYOUNFLObxfWG9T8943Y8Z1gE5WiBLejpwiuwi/AfWIN1GfgLdYGStpqk 2NsamADJ16xW7BYNbzdaG1klRwYdXvsJTrwstBXmNGb3031mzO7Yf3IMnUSDOicp6t oo11+0H/xSEHticPyjatUmQJbxNqgK3Ms99eeF1E= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106922] [12 Regression] Bogus uninitialized warning on boost::optional<>>, missed FRE Date: Wed, 21 Sep 2022 06:55:19 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 12.2.1 X-Bugzilla-Keywords: diagnostic, missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created 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=3D106922 --- Comment #13 from Richard Biener --- Created attachment 53597 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D53597&action=3Dedit candidate patch For reference this is the patch I was talking about. I'm sure I've made a mistake in reasoning but I've not yet nailed it ;) Let's leave the issue in this PR. If you have spare cycles to do another bisection that might help as well. = If your real code doesn't use LTO then bisecting preprocessed source from the affected TU might be also interesting (but I suppose the issue might affect multiple TUs?)=