From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10906 invoked by alias); 6 May 2010 16:37:47 -0000 Received: (qmail 10810 invoked by uid 48); 6 May 2010 16:37:26 -0000 Date: Thu, 06 May 2010 16:37:00 -0000 Message-ID: <20100506163726.10809.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/43990] [OOP] ICE in output_constructor_regular_field, at varasm.c:4995 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "burnus at gcc dot gnu dot org" 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: 2010-05/txt/msg00610.txt.bz2 ------- Comment #4 from burnus at gcc dot gnu dot org 2010-05-06 16:37 ------- (In reply to comment #3) > See also PR 43895 As I feared there: There seems to be an inconsistency with CLASS with POINTER or ALLOCATABLE attribute: Is "class.$DATA" or "class" the pointer variable. If one adds "b = ALLOCATED(x)" one finds: x.a.$data = 0B; ! Default initialization sets class.$data to NULL D.1577 = &x->a; ! ALLOCATED check looks at "(class != NULL)" b = D.1577 != 0B; Which does not make sense. [This might be unrelated to the ICE.] -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43990