From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-173896-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 7268 invoked by alias); 13 Apr 2012 09:47:11 -0000
Received: (qmail 7259 invoked by uid 22791); 13 Apr 2012 09:47:10 -0000
X-SWARE-Spam-Status: No, hits=-4.3 required=5.0	tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE
X-Spam-Check-By: sourceware.org
Received: from mail-ob0-f175.google.com (HELO mail-ob0-f175.google.com) (209.85.214.175)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 13 Apr 2012 09:46:57 +0000
Received: by obbuo13 with SMTP id uo13so4464430obb.20        for <gcc@gcc.gnu.org>; Fri, 13 Apr 2012 02:46:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.111.3 with SMTP id ie3mr1301411obb.14.1334310417016; Fri, 13 Apr 2012 02:46:57 -0700 (PDT)
Received: by 10.182.51.234 with HTTP; Fri, 13 Apr 2012 02:46:56 -0700 (PDT)
Date: Fri, 13 Apr 2012 09:47:00 -0000
Message-ID: <CAH6eHdTLte1F+KvjrzVxsHGh-pucXKmGVDMT1d7F=4338-zqvw@mail.gmail.com>
Subject: Concurrency items in C++11 status table
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: gcc@gcc.gnu.org
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
X-SW-Source: 2012-04/txt/msg00573.txt.bz2

The table at http://gcc.gnu.org/projects/cxx0x.html indicates most of
the concurrency work is not done, but I think the status is better
than it shows.

If I'm not mistaken strong CAS and bidirectional fences are done.

Does anything need to be done for atomics in signal handlers?

at_quick_exit() is available in glibc, is anything needed from GCC?

Are any compiler changes needed for sequence points, or is it just a
re-wording of existing rules to make sense in a multi-threaded world?