https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
Florian Weimer changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
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 #11 from Jonathan Wakely ---
(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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #10 from Jonathan Wakely ---
Ah, it works for C++ because of r12-5108-g80fe172ba98201
With a recent glibc __gthread_cond_timedwait just calls pthread_cond_timedwait
directly, so use correctly redirected to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Ever confirmed|0
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 #5 from Jonathan Wakely ---
The description is a bit confusing, but the issue is that we define:
typedef struct timespec __gthread_time_t;
and then use that in several functions like this:
static inline int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109540
--- Comment #4 from Jonathan Wakely ---
Yes, I know. I'm just pointing out that you're reporting a bug against an
unsupported version.
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 #2 from Jonathan Wakely ---
N.B. GCC 9 is no longer supported, so any changes will not help that version.
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
14 matches
Mail list logo
