https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83853
--- Comment #4 from rene.r...@fu-berlin.de ---
(In reply to Jonathan Wakely from comment #3)
> (In reply to rene.rahn from comment #2)
> > It basically says, that while T2 is currently destroying the condition
> > variable, T1 is still accessing i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83853
Jonathan Wakely changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83853
--- Comment #2 from rene.r...@fu-berlin.de ---
Hi,
sorry I submitted accidentally before writing the text.
I am investigating some use cases for condition_variables using c++11 thread
support library.
In my use case I have the following setup.
2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83853
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
