public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gerald at pfeifer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/35114] New: 731 unexpected libgomp testsuite failures due setup of test environment
Date: Wed, 06 Feb 2008 21:34:00 -0000 [thread overview]
Message-ID: <bug-35114-231@http.gcc.gnu.org/bugzilla/> (raw)
Running the testsuite on i386-unknown-freebsd6.2 I noticed the following:
=== libgomp Summary ===
# of expected passes 88
# of unexpected failures 731
# of unsupported tests 109
(Cf. http://gcc.gnu.org/ml/gcc-testresults/2008-02/msg00301.html for details.)
Looking into libgomp.log.sent, I see the following pattern:
/usr/bin/ld: warning: libgcc_s.so.1, needed by
/usr/nabil-files/pfeifer/OBJ-0206
-0128/i386-unknown-freebsd6.2/./libgomp/.libs/libgomp.so, not found (try using
-
rpath or -rpath-link)
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__mulxc3@GCC_4.0.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__mulsc3@GCC_4.0.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__divsc3@GCC_4.0.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__divdi3@GCC_3.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__muldc3@GCC_4.0.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__moddi3@GCC_3.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__divdc3@GCC_4.0.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__udivdi3@GCC_3.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__divxc3@GCC_4.0.0'
/usr/nabil-files/pfeifer/OBJ-0206-0128/i386-unknown-freebsd6.2/./libgomp/../libg
fortran/.libs/libgfortran.so: undefined reference to `__umoddi3@GCC_3.0'
This problem does not happen for the other frontends/libraries, so I
assume it is a libgomp-specific issue with the testsuite.
--
Summary: 731 unexpected libgomp testsuite failures due setup of
test environment
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgomp
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: gerald at pfeifer dot com
GCC build triplet: i386-unknown-freebsd6.2
GCC host triplet: i386-unknown-freebsd6.2
GCC target triplet: i386-unknown-freebsd6.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35114
next reply other threads:[~2008-02-06 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 21:34 gerald at pfeifer dot com [this message]
2009-01-25 20:40 ` [Bug testsuite/35114] " gerald at pfeifer dot com
2009-02-03 10:03 ` gerald at pfeifer dot com
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=bug-35114-231@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).