public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/100748] [12 regression] 30_threads/jthread/95989.cc fails after r12-843
Date: Thu, 09 Sep 2021 03:06:57 +0000	[thread overview]
Message-ID: <bug-100748-4-XMV6Z0wdzS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100748-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100748

--- Comment #4 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Bernd E. analyzed this in the thread referenced in c#1.

The test links staticly and we're pulling in the weak definition of
pthread_join.

I'm not sure why we're linking statically.  Reverting to normal dynamic linking
would likely fix this problem.

If that's not desired, then something like --whole-archive -lpthread
--no-whole-archive in the link line will make this work as long as it appears
before -lc.

Or we could add -Wl,-u,pthread_join to the link line.

Or we could hack up the source per Bernd's patch in that thread.

No strong opinions here.  Just trying to get another failure resolved on our
target :-)

  parent reply	other threads:[~2021-09-09  3:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-24 20:58 [Bug testsuite/100748] New: " seurer at gcc dot gnu.org
2021-05-24 21:11 ` [Bug testsuite/100748] " redi at gcc dot gnu.org
2021-05-24 21:27 ` seurer at gcc dot gnu.org
2021-05-24 23:47 ` redi at gcc dot gnu.org
2021-05-25  7:43 ` rguenth at gcc dot gnu.org
2021-09-09  3:06 ` law at gcc dot gnu.org [this message]
2021-09-09  6:35 ` redi at gcc dot gnu.org
2021-10-09  0:26 ` redi at gcc dot gnu.org
2021-10-09  5:07 ` law at gcc dot gnu.org
2021-10-09  7:07 ` redi at gcc dot gnu.org
2021-11-09 20:05 ` redi at gcc dot gnu.org
2021-11-10 12:04 ` cvs-commit at gcc dot gnu.org
2021-11-10 12:08 ` redi at gcc dot gnu.org
2021-11-24 11:52 ` cvs-commit at gcc dot gnu.org
2022-08-03 12:30 ` cvs-commit at gcc dot gnu.org
2022-08-03 13:33 ` redi 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-100748-4-XMV6Z0wdzS@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).