From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12410 invoked by alias); 30 Sep 2010 09:25:01 -0000 Received: (qmail 12400 invoked by uid 22791); 30 Sep 2010 09:25:00 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,MISSING_MID 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; Thu, 30 Sep 2010 09:24:56 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45827] mio_component_ref(): Component not found when mixing f90 and f03 in large projects 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: WAITING X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.6.0 X-Bugzilla-Changed-Fields: 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: Thu, 30 Sep 2010 10:44: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-09/txt/msg03205.txt.bz2 Message-ID: <20100930104400.446g2nqTvhwcxx48UUZaXY7H2cIQnKFHMiD7cPX7SDk@z> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45827 --- Comment #12 from Tobias Burnus 2010-09-30 09:24:49 UTC --- (In reply to comment #11) > So it works with 4.6.0 20100924, but it still doesn't work with 4.6.0 20100921. > Unfortunately, I cannot use the latest revision, until bug 45746 is fixed. Actually, I am confused: From that comment it sounds as if 20100921 does not have the bug 45746 - but it has been reported using 20100921 and a comment by Dominique indicates that it never worked with GCC 4.5/4.6 but it only worked for a while on the fortran-dev branch. > Plus, I assume that the error message will show up in later revisions again. Any reason why you think that this will be the case? (In reply to comment #0) > I use the actual GNU Fortran (GCC) 4.6.0 20100928. But it already happened, > that the bug disappeared and appeared again. Such bugs are usually an indication for not properly initialized memory. Especially when it happens, it helps if one can try valgrind on the file: valgrind `gfortran -v 2>&1 | grep f951` Memory related errors tend to show up only on few machines and in irregular patterns, which makes finding them difficult.