From: Gerald Pfeifer <gerald@pfeifer.com>
To: fortran@gcc.gnu.org, gcc@gcc.gnu.org
Cc: Janis Johnson <janis187@us.ibm.com>
Subject: Fortran-related libgomp failures in case of -fno-openmp
Date: Mon, 01 Jun 2009 17:59:00 -0000 [thread overview]
Message-ID: <alpine.LSU.1.99.0906011954250.27711@acrux.dbai.tuwien.ac.at> (raw)
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
next reply other threads:[~2009-06-01 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 17:59 Gerald Pfeifer [this message]
2009-06-01 18:14 ` Steve Kargl
2009-06-01 19:49 ` Janis Johnson
2009-06-01 20:21 ` Steve Kargl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.1.99.0906011954250.27711@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=janis187@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).