public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/114646] libgcc's gthr.h still defines GTHREAD_USE_WEAK to 1 for newer glibc
Date: Mon, 08 Apr 2024 20:22:13 +0000	[thread overview]
Message-ID: <bug-114646-4-d33t9879DX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114646-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> What was done for libstdc++ was only specific to libstdc++ even though it
> uses the same headers, it was not changed for the generic libgcc code which
> is used in other places including but not limited to the unwinder, and
> libobjc. now the question comes to do we want to bring in pthread_ functions
> always with the unwinder? I don't know ...

For glibc, most of these functions are included in minimal static executables
anyway. At least today, the difference is not going to be large, if it exists
at all. In the future, minimal static executables may have a smaller footprint,
but even then, these functions are pretty small. The concern is probably more
in the opposite direction, that pthread_once pulls in the unwinder …

  parent reply	other threads:[~2024-04-08 20:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 20:03 [Bug libfortran/114646] New: libgfortran doesn't work with static libpthread hjl.tools at gmail dot com
2024-04-08 20:05 ` [Bug libfortran/114646] " hjl.tools at gmail dot com
2024-04-08 20:07 ` pinskia at gcc dot gnu.org
2024-04-08 20:07 ` pinskia at gcc dot gnu.org
2024-04-08 20:10 ` fw at gcc dot gnu.org
2024-04-08 20:11 ` [Bug libfortran/114646] libgcc's gthr.h still defines GTHREAD_USE_WEAK to 1 for newer glibc pinskia at gcc dot gnu.org
2024-04-08 20:15 ` [Bug libgcc/114646] " pinskia at gcc dot gnu.org
2024-04-08 20:18 ` hjl.tools at gmail dot com
2024-04-08 20:22 ` fw at gcc dot gnu.org [this message]
2024-04-08 21:36 ` pinskia at gcc dot gnu.org
2024-04-08 21:43 ` hjl.tools at gmail dot com
2024-04-08 21:45 ` bruno at clisp dot org
2024-04-08 21:46 ` [Bug libfortran/114646] libgfortran still doesn't define GTHREAD_USE_WEAK to 0 " hjl.tools at gmail dot com
2024-04-08 21:50 ` pinskia at gcc dot gnu.org
2024-04-08 21:51 ` pinskia at gcc dot gnu.org
2024-04-08 21:53 ` hjl.tools at gmail dot com
2024-04-08 21:58 ` pinskia at gcc dot gnu.org
2024-04-08 22:02 ` pinskia at gcc dot gnu.org
2024-04-09 17:03 ` skpgkp2 at gmail 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-114646-4-d33t9879DX@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).