From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19719 invoked by alias); 8 Nov 2010 14:39:19 -0000 Received: (qmail 19630 invoked by uid 22791); 8 Nov 2010 14:39:19 -0000 X-SWARE-Spam-Status: No, hits=-2.8 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; Mon, 08 Nov 2010 14:39:15 +0000 From: "janus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/46344] [4.6 Regression] [OOP] ICE with allocatable CLASS components X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: janus at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: janus at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Mon, 08 Nov 2010 14:39:00 -0000 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-11/txt/msg00944.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46344 --- Comment #12 from janus at gcc dot gnu.org 2010-11-08 14:39:01 UTC --- (In reply to comment #11) > The error seems to be sensitive to the first letter of the type(t1) variable. > All names starting with 'w'-'z' fail, others seem to work. Also the error > disappears when adding "implicit none", so it seems to be connected to implicit > typing. After some more research I came to the conclusion that it's rather a resolution problem: Sometimes symbols for class containers and vtabs are generated at resolution stage. If this happens while traversing a namespace's symbol tree, symbols are being added and the tree is rearranged, so that the traversing routine may miss some symbols! This is also the reason why this error occurs so randomly: It depends on how the tree is being rearranged and whether we're lucky enough to still resolve all symbols!