From: Josiah Worcester <josiahw@gmail.com>
To: musl@lists.openwall.com
Subject: Re: the case for __MUSL__
Date: Mon, 29 Dec 2014 11:15:16 -0600 [thread overview]
Message-ID: <CAMAJcuCaGdgwTycOfiaApNRH1yvyQar7BmLHPUxheujgJnVtwQ@mail.gmail.com> (raw)
In-Reply-To: <F4BC7730-8BE9-48C0-BE2A-56351E4D795C@cognitive-electronics.com>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Dec 29, 2014 10:27 AM, "Richard Gorton" <
rcgorton@cognitive-electronics.com> wrote:
>
>
> Hi,
>
> I'm working on getting C++ working for our target: we use clang, and
libcxx/libcxxabi libraries from llvm.org
> it seems to me (as I'm doing this) that instead of doing things like
>
> // Our compiler defines __COGNITIVE__
> #if defined(__COGNITIVE__)
>
> It would make more sense to use
>
> #if defined(__MUSL__)
>
>
> I'm not proposing/suggesting use of this within musl itself, but for use
in other libraries (such as libcxx) which 'know' about the internal
implementation of libc.
> Thoughts & Comments appreciated
>
>
>
> An example case is in libcxx/src/locale.cpp, where there are bits of code
related to accessing the current locale:
>
I suspect the thing to do here is more to iterate over the set of chars and
construct the table as needed: there's no sensible interface to this bit of
functionality in a standard way (and musl to my knowledge doesn't have the
table you want exposed anywhere). Note that doing it that way ought to just
work anywhere.
[-- Attachment #2: Type: text/html, Size: 1402 bytes --]
next prev parent reply other threads:[~2014-12-29 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 16:27 Richard Gorton
2014-12-29 17:15 ` Josiah Worcester [this message]
2014-12-29 17:17 ` Josiah Worcester
2014-12-29 17:37 ` Rich Felker
2014-12-29 17:51 ` Richard Gorton
2014-12-29 17:59 ` Josiah Worcester
2014-12-29 21:29 ` Justin Cormack
2014-12-29 21:55 ` 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=CAMAJcuCaGdgwTycOfiaApNRH1yvyQar7BmLHPUxheujgJnVtwQ@mail.gmail.com \
--to=josiahw@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).