From: Jens Gustedt <jens.gustedt@inria.fr>
To: musl@lists.openwall.com
Subject: Re: C threads, v. 6.2
Date: Sun, 31 Aug 2014 09:09:22 +0200 [thread overview]
Message-ID: <1409468962.4476.268.camel@eris.loria.fr> (raw)
In-Reply-To: <20140831024429.GA13259@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 2039 bytes --]
Am Samstag, den 30.08.2014, 22:44 -0400 schrieb Rich Felker:
> On Sat, Aug 30, 2014 at 09:31:11PM -0400, Rich Felker wrote:
> > On Sat, Aug 30, 2014 at 08:30:34PM -0400, Rich Felker wrote:
> > > > For the C thread TU, what would be the mechanics for them to call one
> > > > of the (aliased) pthread functions?
> > >
> > > With my alternate solution just described, simply including the normal
> > > pthread header and casting the pointer when making the call would be
> > > fully legal.
> > >
> > > With the approach we previously discussed, where we have to ensure
> > > that no TU that accesses the contents of a mutex or cv structure can
> > > see both the C11 and POSIX versions, The C11 TUs would have to contain
> > > prototypes for the aliased POSIX functions like:
> > >
> > > int __pthread_mutex_lock(mtx_t *);
> > >
> > > Note that this is a perfectly correct prototype because mtx_t is just
> > > this TU's typedef name for the tagless "struct { union { ... } __u; }"
> > > that it's using, which is "the same type" as pthread_mutex_lock.c's
> > > pthread_mutex_t.
> >
> > Actually, unless the C11 functions actually access the mutex object,
> > their implementation files don't need to avoid having both types
> > visible. Only the TUs that dereference the object (i.e. the pthread
> > ones) need to ensure that only one version of the type is visible.
>
> The more I think about it, the more I think the visibility of the
> other type is utterly irrelevant.
Yes, inside the C thread implementation it is. So as you have seen I
already came to the same conclusion, and so I applied that idea to the
latest series of patches.
I think this discussion is settled, then.
Jens
--
:: INRIA Nancy Grand Est ::: AlGorille ::: ICube/ICPS :::
:: ::::::::::::::: office Strasbourg : +33 368854536 ::
:: :::::::::::::::::::::: gsm France : +33 651400183 ::
:: ::::::::::::::: gsm international : +49 15737185122 ::
:: http://icube-icps.unistra.fr/index.php/Jens_Gustedt ::
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-08-31 7:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 22:11 Jens Gustedt
2014-08-27 23:46 ` Rich Felker
2014-08-28 9:40 ` Jens Gustedt
2014-08-28 11:41 ` Szabolcs Nagy
2014-08-28 16:15 ` Rich Felker
2014-08-28 19:28 ` Jens Gustedt
2014-08-28 20:00 ` Rich Felker
2014-08-28 20:55 ` Szabolcs Nagy
2014-08-28 21:38 ` Jens Gustedt
2014-08-28 21:34 ` Jens Gustedt
2014-08-28 21:56 ` Rich Felker
2014-08-28 23:25 ` Jens Gustedt
2014-08-28 23:38 ` Rich Felker
2014-08-29 7:56 ` Jens Gustedt
2014-08-29 8:02 ` Jens Gustedt
2014-08-29 15:57 ` Rich Felker
2014-08-29 19:01 ` Jens Gustedt
2014-08-30 5:30 ` Rich Felker
2014-08-30 7:43 ` Jens Gustedt
2014-08-30 8:54 ` Jens Gustedt
2014-08-31 0:30 ` Rich Felker
2014-08-31 1:31 ` Rich Felker
2014-08-31 2:44 ` Rich Felker
2014-08-31 7:09 ` Jens Gustedt [this message]
2014-08-29 15:56 ` Rich Felker
2014-08-29 18:40 ` Jens Gustedt
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=1409468962.4476.268.camel@eris.loria.fr \
--to=jens.gustedt@inria.fr \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).