From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5AD39383E825; Sun, 14 Jun 2020 12:54:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5AD39383E825 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1592139275; bh=qjkXNQq0yecjRxbQ2E17M/CkrJjCcYdue7Qg9J89Xi8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=w0OKkFwgbEWzCR0DkJgzXuP8a5kHQRrUrS+RB/ZPdlOvCE+vaagOtAgqZTwtkt8Fe YEWFHNtO1KPS58tgjQygcw3qA9e2uGR0Li9cOzqZ50Tmk3ewNpD0Qkb9BqGj9aEEzP /I2IZG+VnQdVKfe1tXU3SrdeFHuPBtEhEY/LV3jo= From: "tkoenig at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/95512] gcc/fortran/trans-decl.c:1066: array sanity check after use Date: Sun, 14 Jun 2020 12:54:35 +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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tkoenig at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: resolution cc bug_status Message-ID: In-Reply-To: References: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jun 2020 12:54:35 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95512 Thomas Koenig changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID CC| |tkoenig at gcc dot gnu.org Status|WAITING |RESOLVED --- Comment #5 from Thomas Koenig --- I don't think it is necessary to change the code to avoid false positives like this. Hence, closing. However, it was good to raise the issue so it could be checked. Thanks!=