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 76AD138708F0; Thu,  4 Jun 2020 19:17:27 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 76AD138708F0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1591298247;
 bh=NN1m6Ei0G5bUMNgFufECTbOIMqSZXtPDq5BqZCxW0Uo=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=s2oAZeGmnFdzACoQHsRA/N7f43ANMLQBmq2ZVISaLZRDNiH/wA6XrCzDZC2Gqf65T
 cw/bSmljv2QRnCg10CMpTyleTz+ZV/Olry+4fDuvFLJcc7fYy6V705o4TZv7EiNjXH
 SBH6ioZ8WkttziH7k4MedYXjj08J1UbdZuPOxBkI=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95516] [coroutines] incorrect warning "'coro.gro' is used
 uninitialized"
Date: Thu, 04 Jun 2020 19:17:27 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: everconfirmed cf_reconfirmed_on bug_status
Message-ID: <bug-95516-4-1ICJ8lXRu9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95516-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95516-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
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Jun 2020 19:17:27 -0000

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

Iain Sandoe <iains at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2020-06-04
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
Thanks for the report.

this is a kinda tricky situation;
I have also seen this occur (in larger test cases)

1) the coro.gro variable is an internal one to the compiler (it is also mar=
ked
as such). So the user can't "fix" the problem...

2) coro.gro is always initialised unconditionally in the same fragment of c=
ode
that creates it.

so it seems a false positive (actually, the example code posted here does n=
ot
fail for me on either 10.x or master) - however, as noted, I have seen this
occur.

- so this is a problem with the subsequent diagnostics processing or
optimisation.=