From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-368944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 749 invoked by alias); 28 Sep 2011 15:03:17 -0000
Received: (qmail 740 invoked by uid 22791); 28 Sep 2011 15:03:16 -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 15:03:00 +0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50541] gfortran should not accept a pointer as a generic-name   (r178939)
Date: Wed, 28 Sep 2011 15:17: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: burnus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: CC
Message-ID: <bug-50541-4-XsvDfYx2sP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50541-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50541-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/msg02121.txt.bz2

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

Tobias Burnus <burnus at gcc dot gnu.org> changed:

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

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-09-28 15:02:02 UTC ---
(In reply to comment #2)
> What is special about this, is that the generic and the specific procedure
> share the same name. I think the problem is that we only have one symbol for
> both, which triggers the conflict.

I think one could solve this at parse time. When parsing POINTER and
sym->attr.generic and gfc_ns_current->proc_name != sym, we set the attribute to
an interface block. Ditto when parsing "INTERFACE <generic_name>": If one has
already sym->attr.pointer, it is a bug. That should work without further
changes.

Regarding the constructor patch (PR 39427): At least with my current draft
patch does not use a different symbol.