libgomp/fortran test questions.

[IainS <developer at sandoe-acoustics dot co dot uk>]

Hi,

on darwin8 [10.4.11]
.. and with the freshly built compiler uninstalled ..
I get two sets of "make check" fails under libgomp.

libgomp.fortran/crayptr2.f90 [for each torture case]
libgomp.fortran/pr32550.f90 [for each torture case]

both contain
! { dg-options "  ...... -static-libgcc" { target *-*-darwin* } }

I am trying to track down what is happening (which is not  
particularly transparent in the testsuite).

It seems that:
libgomp.1.dylib contains a reference to libgcc_s.1.dylib.

and somehow (even with an apparently correct LD_LIBRARY_PATH) this  
(possibly secondary?) reference to libgcc is not being satisfied.

the compile line contains both -shared-libgcc and -static-libgcc (but  
the static one is last - so I believe it should prevail).

---

what is the intent of specifying both a dynamic linkage (implied by  
libgomp.1.dylib) and a static linkage (-static-libgcc) ?

---

the unresolved symbol (___udivdi3) *is* present in gcc/libgcc_s. 
10.4.dylib, gcc/libgcc_s.1.dylib and gcc/libgcc.a

however, these are not being found - and this symbol is *not* present  
in  /usr/lib/libgcc_s.1.dylib  -- which will be the fall-back for dyld.

====

I've used LD_TRACE_DYLIBS and LD_TRACE_ARCHIVES - and it would seem  
that libgcc_eh.a is being loaded -- but NOT libgcc.a


similarly, if I zap the { target *-*-darwin* }  from the testcase,  
libgcc_s.10.4.dylib is loaded -- but NOT libgcc_s.1.dylib (which is  
referenced by  libgcc_s.10.4.dylib)

====

can anyone point me towards where I should be looking to debug this  
further?

on darwin9 it *appears* to work OK - but this might simply be because  
the /usr/lib/libgcc_s.1.dylib contains the ___udivdi3 symbol anyway.

====

I'm building/checking 142487 at the moment - so no more debugging  
until tomorrow...

Iain