From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 033A4385117A; Thu, 15 Sep 2022 12:12:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 033A4385117A
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1663243927;
	bh=QQWw2WvSLc+hGQd0ipK8n4miV1p4LkVEmQiIubRBrYM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lyglqZ/v8VxPrb19wzuJ6/cX6RQYTxCsV5SGv7fAigt2Ut+yt2hpPI9tZ9lWU/ags
	 73qIoYbkpkhmwhjU/TMUDn/kx9j9JpPQxA7H9y+vS802Kydj9cJdENK2hLea2Tf/Xe
	 dvycZAZxtn3oHGQAw8e0uK/9Ri+LtzAMTDeUhNis=
From: "jan.zizka at nokia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106922] [12/13 Regression] Bogus
 uninitialized warning on boost::optional<<std::vector<std::string>>>, missed
 FRE
Date: Thu, 15 Sep 2022 12:12:06 +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: jan.zizka at nokia dot com
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: 
Message-ID: <bug-106922-4-KC9Jy9oP4J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-106922-4@http.gcc.gnu.org/bugzilla/>
References: <bug-106922-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D106922

--- Comment #7 from Jan =C5=BDi=C5=BEka <jan.zizka at nokia dot com> ---
> Thanks a lot for opening this bugreport!

You are welcome! :-) Unfortunately I'm not familiar with gcc internals that
much in order to comment on the analysis :-(. But once there will be patch =
for
this issue I can quickly try that on our production code.=