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 57BB73857C79; Sun, 26 Jul 2020 07:58:17 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 57BB73857C79
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1595750297;
 bh=wjH9j5aB8u6Yp7cjhvjI5KxbjhU2MHBEWOH9CKunGyE=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=uYYy6mDY3uHgCUoPxp6ONDzbJ1STAOu/Kko8adoh8pXOUMOYV6nXhnLjJ6sw5OwkQ
 1EXDgwVUl2BBLIPkCHWd2U4pIn1wyLJzAK1NyyS1JS93x0EtPCT0UCUg6aj+MVqv5M
 Prqef2jBcgMDa7ed6pjRA+6t0fwcXZ6Uc++uo5C0=
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/94978] [8/9/10/11 Regression] Bogus warning "Array
 reference at (1) out of bounds in loop beginning at (2)"
Date: Sun, 26 Jul 2020 07:58:17 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.4.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: assigned_to bug_status
Message-ID: <bug-94978-4-8Kx5qYysjt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-94978-4@http.gcc.gnu.org/bugzilla/>
References: <bug-94978-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: Sun, 26 Jul 2020 07:58:17 -0000

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

Thomas Koenig <tkoenig at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |tkoenig at gcc dot =
gnu.org
             Status|NEW                         |ASSIGNED

--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Let's see what can be done about this.(In reply to Thomas Koenig from comme=
nt
#2)
> Two ways to fix this: When checking for outer do loops, also check
> if the inner one will be executed at all.
>=20
> Or PR 90302, which is looking more attractive than ever.=