public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/115421] Multi-threaded condition_variable app throws when linking as -static on Linux
Date: Mon, 10 Jun 2024 17:42:33 +0000	[thread overview]
Message-ID: <bug-115421-4-MPjfvuwp7e@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115421-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #3)
> This works fine with glibc 2.34 and above.

I should say with glibc 2.34 and above and GCC 13+.
Other combinations are know to fail since you need to link in the whole
libpthread as there are weak symbols used to detect if the program was single
threaded or not.

  parent reply	other threads:[~2024-06-10 17:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 17:32 [Bug libstdc++/115421] New: " ilg at livius dot net
2024-06-10 17:35 ` [Bug libstdc++/115421] " pinskia at gcc dot gnu.org
2024-06-10 17:36 ` pinskia at gcc dot gnu.org
2024-06-10 17:38 ` pinskia at gcc dot gnu.org
2024-06-10 17:42 ` pinskia at gcc dot gnu.org [this message]
2024-06-10 17:56 ` ilg at livius dot net
2024-06-10 18:00 ` pinskia at gcc dot gnu.org
2024-06-10 18:08 ` pinskia at gcc dot gnu.org
2024-06-10 18:13 ` ilg at livius dot net
2024-06-10 18:16 ` sjames at gcc dot gnu.org
2024-06-10 18:22 ` ilg at livius dot net
2024-06-10 18:26 ` ilg at livius dot net
2024-06-10 18:49 ` ilg at livius dot net
2024-06-10 18:52 ` pinskia at gcc dot gnu.org
2024-06-11  9:26 ` redi at gcc dot gnu.org
2024-06-11  9:27 ` redi at gcc dot gnu.org
2024-06-11  9:39 ` rguenth 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-115421-4-MPjfvuwp7e@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).