On 2021-03-23 09:35, Jonathan Wakely wrote:
On 23/03/21 09:26 -0700, Thiago Macieira via Libstdc++ wrote: On
Tuesday, 23 March 2021 08:39:43 PDT Thomas Rodgers wrote: I will be
submitting a new patch for the
atomic.wait/barrier/latch/semaphore functionality a bit later today
that
subsumes the changes to atomic_wait and latch, and includes the changes
to barrier.
Thanks, Thomas
Is that meant to be part of GCC 11's release?
Yes.
If not, what do we do about preventing the future BC break and
potential
heisenbugs?
1) do nothing, accept they will happen silently
This is our current policy for experimental features and it isn't
going to change for GCC 11.
2) cause non-silent BC breaks
3) disable the code for now (unless explicitly opted-in)
-- Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel DPG Cloud Engineering
FWIW, I would like to commit to an ABI for this with GCC12 and
everything currently residing in the __detail namespace would be moved
into the .so as part of that (likely with a third, and ideally final,
rewrite).
