This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/53015] free_pi_tree(): Unresolved fixup is back
- From: "brainschrat at gmx dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 30 Apr 2012 13:01:21 +0000
- Subject: [Bug fortran/53015] free_pi_tree(): Unresolved fixup is back
- Auto-submitted: auto-generated
- References: <bug-53015-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53015
--- Comment #7 from brainschrat at gmx dot de 2012-04-30 13:01:21 UTC ---
I fixed up my delta script as I now finaly understood what it did:
#! /bin/sh
cp input.f90 /home/staff/paul/noo/src
make -C /home/staff/paul/noo DEBUG=1 lib
cp /home/staff/paul/noo/include/*.mod ./
cp /home/staff/paul/noo/testsuite/bugs/delta/gugv_ass_test_noo.f90 ./
mpif90 -c gugv_ass_test_noo.f90 2>&1 | grep -q fixup
if ! test $? = 0; then
exit 1
fi
exit 0
The point is that the problematic file (matlib.f90) has to be compiled in the
original source directory using the original Makefile, because the error cannot
be reproduced reliably. Then the generated modules are moved to the current
directory and the problematic test case is compiled.
Now delta proceeds to remove ALL lines of code, so something is still wrong.
What are temporary source files in delta iterations called? (This is the file I
have to cp to src/matlib.f90.)