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 41B0D385842D; Wed,  6 Oct 2021 16:44:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 41B0D385842D
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102192] Curious '-O2'-only
 '-Wmaybe-uninitialized' diagnostics for 'libgomp.oacc-fortran/routine-10.f90'
Date: Wed, 06 Oct 2021 16:44:50 +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.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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: bug_status everconfirmed cc cf_reconfirmed_on
Message-ID: <bug-102192-4-64vkMMIeZq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-102192-4@http.gcc.gnu.org/bugzilla/>
References: <bug-102192-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: <https://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: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Oct 2021 16:44:50 -0000

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1
                 CC|                            |msebor at gcc dot gnu.org
   Last reconfirmed|                            |2021-10-06

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
There are lots of reports about -Wmaybe-uninitialized triggering when it's =
not
expected to.  Some are bugs/limitations in the warning but others are inher=
ent
in the IL the warning works with and can't be avoided given its design.=20
Without a small test case to easily reproduce the suspected problem, given =
the
large number of reports with test cases, it's unlikely that anyone will go =
try
to extract one from a historical Git revision of a test, especially one wri=
tten
in FORTRAN and involving complex control flow, to determine were this one
falls.  I would suggest to include the test in the bug report, along with t=
he
output (as we ask users to do).  Better yet would be reducing the suspected
false positive to a smaller test case, and ideally converting it to C.=