public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "punitb20 at gmail dot com" <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: Tue, 18 Apr 2023 12:59:44 +0000 [thread overview] Message-ID: <bug-109540-4-WsRUZU41FC@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 #6 from Puneet B <punitb20 at gmail dot com> --- its not after refer the wiki, its observed on target where its clear that even after compiling application with -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64 its still calling ___pthread_cond_timedwait More over if i call pthread_cond_timedwait directly its calling __pthread_cond_timedwait64 directly as i already mentioned in this thread. And issue is resolved if i add #defing GTHREAD_USE_WEAK 0 in libgcc/gthr-posix.h it clears that weakref symbol is not working properly during linker stage. both __gthrw_(pthread_cond_timedwait) and pthread_cond_timedwait are expected to invoke same API. let me know if you need any more inputs
next prev parent reply other threads:[~2023-04-18 12:59 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 [this message] 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 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-WsRUZU41FC@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: linkBe 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).