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 3046F386EC79; Mon, 18 May 2020 08:56:39 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3046F386EC79
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1589792199;
 bh=u/wEwIFw5BrSlgCMQb0piSH2O8IflCi5e+cY7j0qqVI=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=PHT4n+jwTr/m4wsTsc5VNAdCMADTuvpXQQUtbmPXzuJUS9hl/5bE6S/zTZ2bz+DJZ
 DLABZm4BMm8pdjkyTDpKAO1C1ifEaP13cRTzsi2v7XVl4APilkdZSg3rd1XVXDspry
 70B913z33YUWnfQeKtl1VxmNCIeimVKoeo2iDU/E=
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: Mon, 18 May 2020 08:56:39 +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: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.5
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: everconfirmed blocked bug_status cf_reconfirmed_on
 cc
Message-ID: <bug-94978-4-Qctq8muBv9@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: Mon, 18 May 2020 08:56:39 -0000

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Blocks|                            |90302
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2020-05-18
                 CC|                            |tkoenig at gcc dot gnu.org

--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Two ways to fix this: When checking for outer do loops, also check
if the inner one will be executed at all.

Or PR 90302, which is looking more attractive than ever.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D90302
[Bug 90302] Implement __builtin_warning=