------- Comment #6 from ubizjak at gmail dot com 2007-10-04 06:48 ------- > And as I told in the bug report, inserting or deleting code suddenly > let the issue vanish. I already tried to reduce this code with the > result that removing dead code fixed the miscompilation.
If this is the case, then providing missing functions would be OK too. They can be dummy functions. gfortran -O2 -march=pentium4 -fforce-addr pr33638.f /tmp/cctJqmAN.o: In function `comunpack_': pr33638.f:(.text+0x47): undefined reference to `rdieee_' pr33638.f:(.text+0x3c9): undefined reference to `gbytes_' pr33638.f:(.text+0x456): undefined reference to `gbytes_' pr33638.f:(.text+0x4df): undefined reference to `gbytes_' pr33638.f:(.text+0x6fc): undefined reference to `gbytes_' pr33638.f:(.text+0x778): undefined reference to `gbyte_' pr33638.f:(.text+0x7aa): undefined reference to `gbyte_' pr33638.f:(.text+0x7f5): undefined reference to `gbyte_' pr33638.f:(.text+0x824): undefined reference to `gbyte_' pr33638.f:(.text+0x85d): undefined reference to `rdieee_' pr33638.f:(.text+0x8dc): undefined reference to `rdieee_' pr33638.f:(.text+0x8f9): undefined reference to `rdieee_' pr33638.f:(.text+0xa3f): undefined reference to `gbytes_' pr33638.f:(.text+0xc1a): undefined reference to `gbyte_' pr33638.f:(.text+0xc49): undefined reference to `gbyte_' /usr/local.uros/lib/gcc/i686-pc-linux-gnu/4.3.0/libgfortranbegin.a(fmain.o): In function `main': /home/uros/gcc-build/i686-pc-linux-gnu/libgfortran/../../../gcc-svn/trunk/libgfortran/fmain.c:21: undefined reference to `MAIN__' collect2: ld returned 1 exit status > I will see what I can do, but do not expect any miracles. > This is from a large software package with ~10^2 functions > and at the end there is a binary output file of several MB which is > either as it should or not :-( If you can step through the executable testcase with gdb and if you can say that "fld(5) value at line XXX is YYY but should be WWW" is enough to find the failure. > As it was not clear to me what information to provide, I asked first > on the gcc mailing list, to no avail, so I provided just some random > information. Well, we have bugzilla to report and manage bugs. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33638
