From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17482 invoked by alias); 25 Jan 2012 11:12:13 -0000 Received: (qmail 17473 invoked by uid 22791); 25 Jan 2012 11:12:13 -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, 25 Jan 2012 11:12:00 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/51995] Polymorphic class fails at runtime Date: Wed, 25 Jan 2012 11:18: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: 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: 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 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: 2012-01/txt/msg02894.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51995 Tobias Burnus changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #3 from Tobias Burnus 2012-01-25 11:11:18 UTC --- (In reply to comment #1) > I confirm that on x86_64-apple-darwin10 from > gcc version 4.6.0 20100723 (experimental) [trunk revision 162456] (GCC) up to > now, gfortran gives the following errors Hmm, it also works for me (on x86_64-unknown-linux-gnu) with 4.6.3 20111212 [gcc-4_6-branch revision 182222] 4.6.3 20120121 [gcc-4_6-branch revision 183121] I tried running gfortran through valgrind (4.7 and 4.6) but that only shows memory leakage. As it does not fail for me, I cannot debug it, sorry.