From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Torvald Riegel <triegel@redhat.com>, Martin Sebor <msebor@gmail.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
libc-alpha@sourceware.org, Martin Sebor <msebor@redhat.com>,
Stefan Liebler <stli@linux.vnet.ibm.com>
Subject: Re: [PATCH v3 0/6] Add support for ISO C11 threads.h
Date: Fri, 31 Mar 2017 13:39:00 -0000 [thread overview]
Message-ID: <4b4ab845-95b4-5fed-58ab-99b02a776a52@linaro.org> (raw)
In-Reply-To: <1490688522.26906.465.camel@redhat.com>
On 28/03/2017 05:08, Torvald Riegel wrote:
> On Mon, 2017-03-27 at 10:10 -0600, Martin Sebor wrote:
>> I've reviewed the DRs and your comments below. I agree with
>> your view and just for clarity provide some additional comments
>> of my own.
>
> Thanks!
>
>> There's been a lot of talk over the last few WG14 meetings about
>> the whole threads section needing an overhaul. I don't know if
>> anyone is actually working on it but if it were to happen (for
>> C2X) there is some risk that an implementation coded to the C11
>> spec not conforming to the cleaned up and improved C2X spec.
>
> I'd hope that they wouldn't deviate from what C++ specifies. I'm
> monitoring C++ changes, including whether anything would result in
> required changes for glibc. IOW, if C doesn't deviate from C++, we
> shouldn't need additional changes just for C.
>
Thanks for both extensive inputs and discussion. From the comments I
see that a current C11 thread based on POSIX could be still be feasible,
however I am not sure if we should prevent its implementation based on
the C2X possible different spec.
In any way, I see that the still pending DR493 should not pose any
implementation issues (we can work out on the wrapper if any other
requirement is posed).
So I would like the input from the community whether implementing C11
in GLIBC is desirable and if current approach based is most correct
one.
next prev parent reply other threads:[~2017-03-31 13:39 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 6/6] Add manual documentation for threads.h 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 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 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 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
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 [this message]
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=4b4ab845-95b4-5fed-58ab-99b02a776a52@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=msebor@gmail.com \
--cc=msebor@redhat.com \
--cc=stli@linux.vnet.ibm.com \
--cc=triegel@redhat.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).