From: Thiago Macieira <thiago.macieira@intel.com>
To: Thomas Rodgers <rodgert@appliantology.com>
Cc: <libstdc++@gcc.gnu.org>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/3] Uncontroversial improvements to C++20 wait-related implementation
Date: Tue, 23 Mar 2021 09:26:05 -0700 [thread overview]
Message-ID: <95092538.BtUSnq0jnV@tjmaciei-mobl1> (raw)
In-Reply-To: <7b6c37eaf5ececeed36c027d16e44cc6@appliantology.com>
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?
If not, what do we do about preventing the future BC break and potential
heisenbugs?
1) do nothing, accept they will happen silently
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
next prev parent reply other threads:[~2021-03-23 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 15:29 Thiago Macieira
2021-03-23 15:39 ` Thomas Rodgers
2021-03-23 16:26 ` Thiago Macieira [this message]
2021-03-23 16:35 ` Jonathan Wakely
2021-03-26 23:53 ` Thomas Rodgers
-- strict thread matches above, loose matches on Subject: below --
2021-03-05 18:21 Thiago Macieira
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=95092538.BtUSnq0jnV@tjmaciei-mobl1 \
--to=thiago.macieira@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=rodgert@appliantology.com \
/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: link
Be 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).