https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #12 from Puneet B ---
Thanks for update , since we are using gcc-2.34 , this need to picked as fix.
but do you seen any side impact of this fix which need to be validated?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #8 from Puneet B ---
could some one provide some pointers here? if its observed in gcc.9.3.0 and
fixed in latest GCC, please point me the same, i will pick and validate quickly
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #7 from Puneet B ---
Any pointers here help to debug further.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #6 from Puneet B ---
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #3 from Puneet B ---
It can be reproduceable in gcc master branch or latest release..dont look at it
as GCC particular version bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #1 from Puneet B ---
Here issue is weakref symbol in gcc not using the __asm_ function pointed by
pthread.h instead its calling directly ___pthread_cond_timedwait which is
exposed by version_symbol in pthread_cond_wait.c of glibc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
Bug ID: 109540
Summary: Y2038: GCC gthr-posix.h weakref symbol invoking
function has impact on time values
Product: gcc
Version: 9.3.0
Status: UNCONFIRMED
Seve
