From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14485 invoked by alias); 18 Apr 2012 15:26:45 -0000 Received: (qmail 14476 invoked by uid 22791); 18 Apr 2012 15:26:43 -0000 X-SWARE-Spam-Status: No, hits=-4.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED,TW_GM 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, 18 Apr 2012 15:25:57 +0000 From: "brainschrat at gmx dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/53015] free_pi_tree(): Unresolved fixup is back Date: Wed, 18 Apr 2012 15:26: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: brainschrat at gmx dot de 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: 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-04/txt/msg01534.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53015 --- Comment #3 from brainschrat at gmx dot de 2012-04-18 15:22:01 UTC --- Maybe this is related to using both -I and -J to the same directory. As I wanted to use delta, I tried to simplify my folder layout for the test case: project - src - lib - testsuite o test_1 o test_2 etc Usually, make is called in project, compiles .f90 files in src and puts all .mod and .o files there as well via -J switch. The bug happens if I compile file B in test_2, but points to file A in src (or rather, A.mod). When I put all files in test_2 for using delta, the bug disappeared. After some tinkering I found out that putting the .mod files anywhere else than src (via -J) works. There is both a -I and a -J to src, directly after one another. If I -I and -J point to the same directory, I get the free pi_tree stuff. Removing the -I (as it is not needed for this purpose) solves the problem. The module files produced by the two different calls have the same number of lines, the same size but the ordering in the file. Should the generation of the module files be deterministic? Are there any known problems with -I an d -J? (I could not find anything in bugzilla.)