public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Torvald Riegel <triegel@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: Rich Felker <dalias@libc.org>,
	libc-alpha@sourceware.org,
	Juan Manuel Torres Palma <j.m.torrespalma@gmail.com>
Subject: Re: C11 threads ABI - mtx_t and cnd_t types
Date: Mon, 06 Oct 2014 16:58:00 -0000	[thread overview]
Message-ID: <1412614679.30642.57.camel@triegel.csb> (raw)
In-Reply-To: <Pine.LNX.4.64.1410061550230.29307@digraph.polyomino.org.uk>

On Mon, 2014-10-06 at 15:52 +0000, Joseph S. Myers wrote:
> On Mon, 6 Oct 2014, Torvald Riegel wrote:
> 
> > On Sat, 2014-08-30 at 22:52 -0400, Rich Felker wrote:
> > > Another issue I have on the ABI for C11 threads pertains to the types
> > > for mtx_t and cnd_t. My understanding, and I agree with this, is that
> > > it was already decided to use the same underlying sizes/alignment, and
> > > for now representations, as the corresponding POSIX types.
> > 
> > I don't remember a decision being made rather than just people
> > expressing their opinion at that time, but maybe I'm wrong.
> > 
> > Anyway, for mtx_t I'm starting to wonder whether a fresh start would
> > indeed be better, with some additional room for expanding the lock
> > representation to state elsewhere.  (That is, mtx_t would at least be
> > pointer-sized.)
> 
> If mtx_t isn't a thin wrapper round pthread_mutex_t, then doesn't that 
> mean cnd_wait and cnd_timedwait can no longer be thin wrappers around the 
> corresponding pthread functions?

Right.  But I suspect we should still be able to reuse most of the
source.



  reply	other threads:[~2014-10-06 16:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27 20:38 C11 threads ABI questions - enum values Rich Felker
2014-08-17  7:15 ` Juan Manuel Torres Palma
2014-08-18 19:49   ` Rich Felker
2014-08-26 11:19     ` Juan Manuel Torres Palma
2014-08-26 14:09       ` Rich Felker
2014-08-18 12:27 ` Alexander Monakov
2014-08-18 19:27   ` Rich Felker
2014-10-01 21:13     ` Roland McGrath
2014-10-01 21:16       ` Rich Felker
2014-10-01 21:30         ` Roland McGrath
2014-10-02  0:17           ` Rich Felker
2014-10-02  7:12             ` Juan Manuel Torres Palma
2014-10-02 14:57               ` Rich Felker
2014-10-02 18:42                 ` Juan Manuel Torres Palma
2014-10-02 21:42             ` Roland McGrath
2014-10-02 22:30               ` Rich Felker
2014-10-03 10:40                 ` Joseph S. Myers
2014-10-03 15:19                   ` Rich Felker
2014-10-03 15:31                     ` Joseph S. Myers
2014-10-03 15:33                       ` Rich Felker
2014-10-03 18:39                         ` Christoph Hellwig
2014-10-03 19:49                           ` Rich Felker
2014-10-04 17:53                             ` Christoph Hellwig
2014-10-04 22:58                               ` Rich Felker
2014-10-05  9:49                                 ` Christoph Hellwig
2014-10-05 16:14                                   ` Rich Felker
2014-10-05 16:23                                     ` Christoph Hellwig
2014-10-23  8:00                                       ` Christoph Hellwig
2014-10-23 16:37                                         ` Rich Felker
2014-10-23 16:38                                           ` Rich Felker
2014-10-23 16:58                                             ` Christoph Hellwig
2014-08-31  2:52 ` C11 threads ABI - mtx_t and cnd_t types Rich Felker
2014-08-31  8:48   ` pinskia
2014-08-31 12:28     ` Rich Felker
2014-10-06 13:18   ` Torvald Riegel
2014-10-06 15:52     ` Joseph S. Myers
2014-10-06 16:58       ` Torvald Riegel [this message]
2014-10-06 17:58     ` Rich Felker
2014-10-07 12:51       ` Torvald Riegel
2014-10-07 13:27         ` Rich Felker
2014-10-07 13:59           ` Torvald Riegel
2014-10-07 14:13             ` Rich Felker

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=1412614679.30642.57.camel@triegel.csb \
    --to=triegel@redhat.com \
    --cc=dalias@libc.org \
    --cc=j.m.torrespalma@gmail.com \
    --cc=joseph@codesourcery.com \
    --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).