From: Joseph Myers <joseph@codesourcery.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH v3 0/6] Add support for ISO C11 threads.h
Date: Tue, 21 Mar 2017 16:49:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1703211644540.8480@digraph.polyomino.org.uk> (raw)
In-Reply-To: <662cb906-1845-1164-5b61-a575c5edfe07@linaro.org>
On Tue, 21 Mar 2017, Adhemerval Zanella wrote:
> > Did you review those C11 DRs related to threads to make sure the
> > implementation behaves properly regarding issues raised in those DRs (and
> > that there are tests of this if applicable)?
> >
> > Current DR log: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2109.htm
> >
>
> Thanks for the link, I will check this out. Do you know off the top of your
> head which ones would be applicable?
It appears to be: 405 414 416 424 449 469 470 479 480 493.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-03-21 16:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 13:40 Adhemerval Zanella
2017-03-21 13:40 ` [PATCH 5/6] Add test cases for ISO C11 threads Adhemerval Zanella
2017-03-21 13:40 ` [PATCH 2/6] Move mutex and condition variable definition to common header Adhemerval Zanella
2017-03-22 22:59 ` Ivo Raisr
2017-03-27 13:43 ` Torvald Riegel
2017-03-27 14:25 ` Adhemerval Zanella
2017-03-28 8:19 ` Torvald Riegel
2017-03-31 13:43 ` Adhemerval Zanella
2017-03-21 13:40 ` [PATCH 4/6] Add C11 threads support Adhemerval Zanella
2017-03-21 13:40 ` [PATCH 1/6] Consolidate pthreadtype.h placement Adhemerval Zanella
2017-03-21 13:48 ` Andreas Schwab
2017-03-21 15:07 ` Adhemerval Zanella
2017-03-21 13:40 ` [PATCH 3/6] Clean pthread functions namespaces for C11 threads Adhemerval Zanella
2017-03-21 13:40 ` [PATCH 6/6] Add manual documentation for threads.h Adhemerval Zanella
2017-03-21 16:25 ` [PATCH v3 0/6] Add support for ISO C11 threads.h Joseph Myers
2017-03-21 16:44 ` Adhemerval Zanella
2017-03-21 16:49 ` Joseph Myers [this message]
2017-03-21 17:08 ` Adhemerval Zanella
2017-03-21 20:10 ` Adhemerval Zanella
2017-03-27 13:29 ` Torvald Riegel
2017-03-27 13:29 ` Torvald Riegel
2017-03-27 16:10 ` Martin Sebor
2017-03-28 8:08 ` Torvald Riegel
2017-03-31 13:39 ` Adhemerval Zanella
2017-04-06 11:05 ` Torvald Riegel
2017-04-06 14:30 ` Adhemerval Zanella
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=alpine.DEB.2.20.1703211644540.8480@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
/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).