public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/109540] Y2038: GCC gthr-posix.h weakref symbol invoking function has impact on time values
Date: Thu, 20 Apr 2023 11:12:44 +0000	[thread overview]
Message-ID: <bug-109540-4-W5idHsE5BH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109540-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #10)
> If you have glibc 2.34 then you can use -DGTHREAD_USE_WEAK=0 to disable the
> weak refs in gthr-posix.h

I think that is indeed the correct fix, as you originally asked about. But only
for glibc 2.34 and later.

  parent reply	other threads:[~2023-04-20 11:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  7:59 [Bug libgcc/109540] New: " punitb20 at gmail dot com
2023-04-18  8:01 ` [Bug libgcc/109540] " punitb20 at gmail dot com
2023-04-18 10:15 ` redi at gcc dot gnu.org
2023-04-18 10:19 ` punitb20 at gmail dot com
2023-04-18 11:12 ` redi at gcc dot gnu.org
2023-04-18 11:19 ` redi at gcc dot gnu.org
2023-04-18 12:59 ` punitb20 at gmail dot com
2023-04-19  6:24 ` punitb20 at gmail dot com
2023-04-20  7:19 ` punitb20 at gmail dot com
2023-04-20 11:04 ` redi at gcc dot gnu.org
2023-04-20 11:11 ` redi at gcc dot gnu.org
2023-04-20 11:12 ` redi at gcc dot gnu.org [this message]
2023-04-20 14:16 ` punitb20 at gmail dot com
2023-05-05 11:46 ` fw at gcc dot gnu.org
2024-04-08 22:11 ` pinskia 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-109540-4-W5idHsE5BH@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).