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 368B63954C4F; Tue, 23 Jun 2020 06:15:21 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 368B63954C4F
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1592892921;
 bh=LwNNJ23p4xsItrFkL9ocg63XFOyeF3UopUPWuhcbK50=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=Xp1iY5wr2RNaM06BIai8Ll3inTfts9ehOgxd/0hey8On07bu5aHz9V75QkjeC/ntE
 ZxigJ5K8SV47IHYj/Wj4GRFS2U8TpL15XNOhkyjhKk+LDEUtB34IajNUGIVSEmFz/2
 rKYb85aTDDC0RhkjD+MV7YytIue17GY1cqToCBxo=
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/95812] [10/11 Regression] ICE in gfc_dep_resolver since
 r10-2114
Date: Tue, 23 Jun 2020 06:15:21 +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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.2
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-95812-4-MSN6Uvt9pO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95812-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: Tue, 23 Jun 2020 06:15:21 -0000

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Thomas K=C3=A0=C2=A4=C2=A5=C3=A0=C2=
=A4nig <tkoenig@gcc.gnu.org>:

https://gcc.gnu.org/g:abcde0a658e17dbbabcb396eaae5a3612e07d401

commit r11-1595-gabcde0a658e17dbbabcb396eaae5a3612e07d401
Author: Thomas Koenig <tkoenig@gcc.gnu.org>
Date:   Tue Jun 23 08:14:51 2020 +0200

    Handle AR_FULL vs. AR_FULL in dependency checking.

    Previously, handling of full vs. full references failed to take
    AR_FULL vs. AR_FULL into account.  A change in dependency
    checking in gcc 10 created a code path that could lead there;
    with this patch, this is now correctly handled.

    gcc/fortran/ChangeLog:

    2020-06-23  Thomas Koenig  <tkoenig@gcc.gnu.org>

            PR fortran/95812
            * dependency.c (ref_same_as_full_array): Handle case of AR_FULL
            vs. AR_FULL.

    gcc/testsuite/ChangeLog:

    2020-06-23  Thomas Koenig  <tkoenig@gcc.gnu.org>

            PR fortran/95812
            * gfortran.dg/dependency_59.f90: New test.=