From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-368983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 6503 invoked by alias); 28 Sep 2011 20:01:19 -0000
Received: (qmail 6476 invoked by uid 22791); 28 Sep 2011 20:01:15 -0000
X-SWARE-Spam-Status: No, hits=-2.9 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 28 Sep 2011 20:00:59 +0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50550] does not recognize pointer variable at initialization (r178939)
Date: Wed, 28 Sep 2011 20:06: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-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: CC
Message-ID: <bug-50550-4-GmQLiY0KHr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50550-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50550-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
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
X-SW-Source: 2011-09/txt/msg02160.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50550

janus at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |janus at gcc dot gnu.org

--- Comment #1 from janus at gcc dot gnu.org 2011-09-28 20:00:54 UTC ---
The cases in comment #0 are rather easily fixable in the current
implementation. However, the harder case will be the following:

integer :: j => null()
pointer :: j
end

because when parsing the init, we don't know yet whether the object is a
pointer or not (which means the check would have to be deferred to resolution
stage).

Looking at F08:R505 and friends, I don't see an obvious reason why any of the
cases listed here should be forbidden.