From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23787 invoked by alias); 27 Apr 2008 13:24:49 -0000 Received: (qmail 23676 invoked by alias); 27 Apr 2008 13:24:03 -0000 Date: Sun, 27 Apr 2008 13:24:00 -0000 Message-ID: <20080427132403.23675.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/36058] Not allowing pointers to derived types in COMMON In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "w6ws at earthlink dot net" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2008-04/txt/msg01920.txt.bz2 ------- Comment #2 from w6ws at earthlink dot net 2008-04-27 13:24 ------- Subject: Re: Not allowing pointers to derived types in COMMON burnus at gcc dot gnu dot org wrote: > ------- Comment #1 from burnus at gcc dot gnu dot org 2008-04-27 08:01 ------- > gfortran's rejection is in line with g95, NAG f95, ifort, openf95, sunf95 and > ifort. On the other side are PGI and Salford/Silverfrost - who allow the pointer to reside in the COMMON block. > Additionally, I think the following also applies to pointers. ("my_wwsptr" is > of a derived type [albeit with pointer attribute].) > > "C589 (R558) If a common-block-object is of a derived type, it shall be a > sequence type (4.5.1) or a type with the BIND attribute and it shall have no > default initialization." I am only concerned with the POINTER case. I am not placing a derived type object in the COMMON block. I am only storing a pointer to it. W. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36058