From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-499018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 92149 invoked by alias); 8 Oct 2015 10:05:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 92095 invoked by uid 48); 8 Oct 2015 10:05:36 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/63158] Possible wrong code with absend optional BT_CLASS -> optional BT_DERIVED dummy argument
Date: Thu, 08 Oct 2015 10:05:00 -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: 5.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
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:
Message-ID: <bug-63158-4-JkSaPmYSaK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63158-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63158-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-10/txt/msg00573.txt.bz2

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

--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I cannot find any file in gcc/fortran containing the string
> "!e->ref->u.ar.type != AR_FULL" for 4.8, 4.9 and trunk (5.0).

It has been replaced with "e->ref->u.ar.type != AR_FULL" at line 5218:

                  if (fsym->attr.optional
                      && e->expr_type == EXPR_VARIABLE
                      && (!e->ref
                          || (e->ref->type == REF_ARRAY
                              && e->ref->u.ar.type != AR_FULL))
                      && e->symtree->n.sym->attr.optional)

Changed by r214827.

> Is this PR still valid?

*PING*!

Should I close this PR as INVALID to get an answer?