public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia.nrc.ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/46967] lots of testsuite failures with libgomp on hppa-hp-hpux11.31
Date: Thu, 27 Jan 2011 20:49:00 -0000	[thread overview]
Message-ID: <bug-46967-4-Gd2FdYSeC8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46967-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46967

--- Comment #2 from dave at hiauly1 dot hia.nrc.ca 2011-01-27 20:24:02 UTC ---
>  With r163461 backported (compiler only built with --enable-languages=c this
> time) we ran the libgomp testsuite 3 times, failed 11/248 tests, 0/248 tests
> and 9/248 tests. So, still not fantastic, but the 0/248 was nice to see.

I believe that libgomp.sl is incorrectly linked:

# chatr libgomp.sl
libgomp.sl:
         shared library
     shared library dynamic path search:
         SHLIB_PATH     disabled  second
         embedded path  enabled   first  /opt/gnu/gcc/gcc-4.5/lib
     internal name:
         libgomp.sl.1
     shared library list:
         dynamic   /usr/lib/librt.2
         dynamic   /usr/lib/libc.2
         dynamic   /mnt/gnu/gcc/objdir/./gcc/libgcc_s.4
         dynamic   /opt/langtools/lib/libpthread.1

As can be seen, libgomp is linked against libc, and libc.2 comes
before libpthread.1 in the shared library list.  libc contains
non functional pthread functions, so it is likely pthread support
is not functional.  From the discussion, it appears there is a
difference in the behavior of the dynamic loader in 11.31 and
other hpux 11 releases.

HP recommends not linking shared libraries against libc.  libtool
adds -lc to the link command.  It doesn't come directly from the libgomp
configuration.  So, libtool needs to be fixed first.

Dave


  parent reply	other threads:[~2011-01-27 20:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 19:12 [Bug libgomp/46967] New: " bugzilla-gcc at thewrittenword dot com
2011-01-27 20:17 ` [Bug libgomp/46967] " bugzilla-gcc at thewrittenword dot com
2011-01-27 20:49 ` dave at hiauly1 dot hia.nrc.ca [this message]
2011-05-01 19:03 ` htl10 at users dot sourceforge.net
2011-05-01 21:38 ` danglin at gcc dot gnu.org
2011-05-01 22:09 ` htl10 at users dot sourceforge.net
2011-05-01 22:26 ` htl10 at users dot sourceforge.net
2011-08-20  5:45 ` bugzilla-gcc at thewrittenword dot com
2011-08-20 17:04 ` dave.anglin at bell dot net
2014-11-25  2:40 ` danglin at gcc dot gnu.org

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-46967-4-Gd2FdYSeC8@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).