This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Fortran-related libgomp failures in case of -fno-openmp


On i386-unknown-freebsd7.1 we see the following tests fail:

  FAIL: libgomp.fortran/condinc2.f  -O  (test for excess errors)
  WARNING: libgomp.fortran/condinc2.f  -O  compilation failed to produce executable
  FAIL: libgomp.fortran/condinc4.f90  -O  (test for excess errors)
  WARNING: libgomp.fortran/condinc4.f90  -O  compilation failed to produce executable
  FAIL: libgomp.fortran/omp_cond2.f  -O  (test for excess errors)
  WARNING: libgomp.fortran/omp_cond2.f  -O  compilation failed to produce executable
  FAIL: libgomp.fortran/omp_cond4.F90  -O  (test for excess errors)
  WARNING: libgomp.fortran/omp_cond4.F90  -O  compilation failed to produce executable

Looking into the log files, the pattern is the same in all cases:

  Excess errors:
  /pfeifer/OBJ-0531-2252/i386-unknown-freebsd7.1/./libgomp/.libs/libgomp.so:
  undefined reference to `pthread_create'

And what all of these three testcases have in common is

  { dg-options "-fno-openmp" }

So, it seems -fno-openmp in combination with an attempt to still link
libgomp.so leads to this failure.


Is it possible this is an issue with the testsuite rather than with
the code on FreeBSD?

Gerald


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]