public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "brainschrat at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
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 [thread overview]
Message-ID: <bug-53015-4-sSw6KVC6Xq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53015-4@http.gcc.gnu.org/bugzilla/>
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.)
next prev parent reply other threads:[~2012-04-18 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 6:30 [Bug fortran/53015] New: " brainschrat at gmx dot de
2012-04-17 9:11 ` [Bug fortran/53015] " burnus at gcc dot gnu.org
2012-04-17 13:51 ` brainschrat at gmx dot de
2012-04-18 15:26 ` brainschrat at gmx dot de [this message]
2012-04-19 12:16 ` janus at gcc dot gnu.org
2012-04-23 11:48 ` brainschrat at gmx dot de
2012-04-23 12:46 ` burnus at gcc dot gnu.org
2012-04-30 13:01 ` brainschrat at gmx dot de
2012-06-01 10:00 ` brainschrat at gmx dot de
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-53015-4-sSw6KVC6Xq@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).