From: Julien Ramseier <j.ramseier@gmail.com>
To: musl@lists.openwall.com
Subject: Re: Issues when building libcxx libcxxabi with MUSL
Date: Thu, 30 Jun 2016 16:36:09 +0200 [thread overview]
Message-ID: <3BEDF5FF-692E-427D-A02C-3950902B9CC7@gmail.com> (raw)
In-Reply-To: <20160630133827.GA15995@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
> Le 30 juin 2016 à 15:38, Rich Felker <dalias@libc.org> a écrit :
>
> Could you cite the specific text you're looking at? The requirement of
> static storage was removed by
> http://austingroupbugs.net/view.php?id=70 <http://austingroupbugs.net/view.php?id=70> but I see nothing allowing
> the use of mutex values or assigning one to another, which as I
> understand it is what the offending libc++ code is doing.
I'm not sure what you mean by "mutex value".
The libcxx mutex class only uses the PTHREAD_MUTEX_INITIALIZER
macro as an initializer for its underlying pthread_mutex member.
The part of the spec I was referring to is the use of
PTHREAD_MUTEX_INITIALIZER to initialize non-static mutexes,
which is what libcxx did and still do with my patch, but in a different
way to avoid the constexpr issue due to the nested volatile types.
[-- Attachment #2: Type: text/html, Size: 5758 bytes --]
next prev parent reply other threads:[~2016-06-30 14:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 19:24 Zhao, Weiming
2016-06-22 19:34 ` Rich Felker
2016-06-22 19:38 ` Julien Ramseier
2016-06-22 19:41 ` Rich Felker
2016-06-30 12:50 ` Julien Ramseier
2016-06-30 13:15 ` Szabolcs Nagy
2016-06-30 13:38 ` Szabolcs Nagy
2016-06-30 13:45 ` Rich Felker
2016-06-30 13:38 ` Rich Felker
2016-06-30 14:36 ` Julien Ramseier [this message]
2016-06-30 14:58 ` 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=3BEDF5FF-692E-427D-A02C-3950902B9CC7@gmail.com \
--to=j.ramseier@gmail.com \
--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).