C++ Logo


Advanced search

[SG5] Fwd: Virtual EWG meeting on transactional memory light TS, Wednesday August 5th @8AM Pacific

From: Hans Boehm <boehm_at_[hidden]>
Date: Wed, 5 Aug 2020 10:42:48 -0700
It was pointed out that the current contextual keyword syntax is ambiguous.
One alternate syntax is

atomic do { ... }

But this needs more email reflector discussion.

Otherwise EWG generally agreed with our direction:

---------- Forwarded message ---------
From: JF Bastien <cxx_at_[hidden]>
Date: Wed, Aug 5, 2020 at 9:43 AM
Subject: Re: Virtual EWG meeting on transactional memory light TS,
Wednesday August 5th @8AM Pacific
To: Evolution Working Group mailing list <ext_at_[hidden]>
Cc: Jens Maurer <Jens.Maurer_at_[hidden]>, Michael Spear <spear_at_[hidden]>,
Michael Wong <fraggamuffin_at_[hidden]>, Hans Boehm <boehm_at_[hidden]>, SG1
concurrency and parallelism <parallel_at_[hidden]>


We met this morning to discuss TM TS v2.

Minutes: https://wiki.edg.com/bin/view/Wg21summer2020/EWG-P1875R0-5-Aug-2020


Use a/many (potentially contextual) keyword to denote atomic blocks, rather
than making it a library feature. For example atomic do { ... }.
5 8 1 0 0

The proposed approach to TM generally seems acceptable, and would fit in a
TM TS v2.
3 12 1 0 0

We'll see it again after discussing the particular keyword approach. LEWG
should also see it to discuss library support guarantees, if any.

On Fri, Jul 31, 2020 at 9:01 AM JF Bastien <cxx_at_[hidden]> wrote:

> Hello atomic { EWG(); }
> Next week, August 5th at 8AM Pacific (3PM GMT), we'll have an EWG telecon
> on the transactional memory light TS:
> - Hans posted links to the EWG reflector yesterday
> <http://lists.isocpp.org/ext/2020/07/14757.php>.
> - The latest background and motivation paper
> <https://isocpp.org/files/papers/P1875R1.pdf> will be in the coming
> mailing (it fixes a few minor issues from the previous version).
> - The wording paper is extremely short
> <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p2066r2.html>.
> Let's discuss it on the reflector first. I expect to hear questions on
> implementations, as well as use of contextual keyword versus other
> approaches.
> Here's the call-in information:
> Zoom Meeting ID 735059607
> Zoom Meeting Password template
> Zoom Meeting Room
> https://iso.zoom.us/j/735059607?pwd=d2tzRkZrTGY1c241R2prOVIrVnNXdz09
> Zoom Meeting Automatic Phone-In US: +16699006833,,735059607# or
> +14086380968,,735059607#
> Zoom Meeting Phone Number US: +1 669 900 6833
> International numbers available https://iso.zoom.us/u/acPWjSNM0

Received on 2020-08-05 12:46:22