Re: problem with gcc 2.95.1 link on linux NFS (NFS/gcc/binutils bug?)

["Alain Coetmeur" <alain dot coetmeur at icdc dot caissedesdepots dot fr>]

Alain Coetmeur a écrit dans le message <7uf0i6$kmu3@puligny.idt.cdc.fr>...
>>>> Recently I've upgraded my suse system to 6.2, and thus upgraded
>>>> egcs to 1.1.2 (from egcs 1.1.1), alias gcc-2.91.66 (from 2.91.60).
>>>> all my large application ... no more run correctly
>>>> and crash with SEGV in unlogical place ...
>>>> without any understandable cause (I've investigated for a long time).
>>>> The only explanation for me is that gcc-2.91.66 introduced a bug
>>>somewhere ...


meanwhile I've installed gcc2.95.1 and made many test and debug...

during one debug session I've noted that some inline base class constructor
were not called, but transforming it into a normal constructor
get things worse, crashing before...

but as soon as I compiled on a local disk instead of my usual
NFS volume (onto a solaris 2.6 server), all get OK magically....

moreover I've noted that the only phase that caused problem
was the g++ linkage.
If I link on a local disk some object compiled on NFS, copied or linked through symblinks,
 then  the binary is running perfectly.

however when I link the objects on a NFS volume, it often don't works
but sometimes does. when it does works the binary are identical according
to "diff", and they are different when it doesn't work.

it is a well known bug of
binutils-2.9.1.0.25-11, of gcc-2.95.1
of of nfs (I'm under suse 6.2 with a kernel 2.2.12 patched with mosix 0.93.03)