From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Issues when building libcxx libcxxabi with MUSL
Date: Thu, 30 Jun 2016 09:45:18 -0400 [thread overview]
Message-ID: <20160630134518.GB15995@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160630133840.GD19691@port70.net>
On Thu, Jun 30, 2016 at 03:38:40PM +0200, Szabolcs Nagy wrote:
> * Szabolcs Nagy <nsz@port70.net> [2016-06-30 15:15:47 +0200]:
> > * Julien Ramseier <j.ramseier@gmail.com> [2016-06-30 14:50:14 +0200]:
> > > A workaround for the C++11 constexpr issue should land soon in libcxx trunk.
> > > http://reviews.llvm.org/D21637 <http://reviews.llvm.org/D21637>
> > >
> >
> > note that without pthread_mutex_destroy it may leak resources.
> >
>
> sorry libc++ uses pthread_mutex_destroy correctly
> (the ~mutex() definition is just in another file).
>
> there is still a nasty conformance issue that affects
> all c++ library implementations: the mutex and thread
> headers include <pthread.h>
They could at least reduce the dependency to sys/types.h with almost
no changes, I think. Better would be including just a proper-sized
buffer and initializing the mutex into it via code in its own TU, not
a public header file.
> it is not valid to include a posix header in c++ code,
> this pollutes the global namespace, might not have valid
> c++ syntax (posix headers are c99) and more importantly
> pthread types are visible through native_handle() which
> makes this impossible to fix.
That can be fixed just by removing them (existence of native handles
is optional).
Rich
next prev parent reply other threads:[~2016-06-30 13:45 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 [this message]
2016-06-30 13:38 ` Rich Felker
2016-06-30 14:36 ` Julien Ramseier
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=20160630134518.GB15995@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).