From: Raphael Cohn <raphael.cohn@stormmq.com>
To: musl@lists.openwall.com
Subject: Re: What would make musl 1.2?
Date: Fri, 13 Feb 2015 14:59:36 +0530 [thread overview]
Message-ID: <CACCP0GohXT5Vk+3Sc0hYajAsmaw_xOaLUhdV9xTcSy2=Tze+_w@mail.gmail.com> (raw)
In-Reply-To: <20150213074603.GA975@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Is there any possibility of adding in the ucontext.h functions? I know
they're deprecated, but they're still widely used - particularly by go for
goroutines, IIRC. I realise there are problems correctly implementing the
*_r variants, but a well-written, modern and efficient implementation would
be a big win.
On 13 February 2015 at 13:16, Rich Felker <dalias@libc.org> wrote:
> We're far enough along in the 1.1.x series now that I'd like to start
> thinking about what milestones might justify calling a release 1.2.0.
>
> Looking at the Open Issues and Roadmap on the wiki, the big things
> musl could gain in the near future look to be:
>
> - Finishing up all the loose ends on locale and multilingual support:
> IDN, message translations, iconv improvements, collation, and
> possibly the byte-based C locale.
>
> - Hardening/security features.
>
> - C++11 non-POD TLS.
>
> - Alternate user/group db backends (hopefully in upcoming 1.1.7).
>
> Any or all of these could become part of the wishlist for 1.2.
>
> Aside from those big functionality areas though, I think archs/porting
> might be one of the most important things to think about. Supporting
> aarch64 is definitely important in the near future, and it could be a
> big publicity boost. So could getting coverage for the remaining archs
> uClibc has that musl doesn't, or at least the ones of modern interest.
>
> Other ideas?
>
> Rich
>
[-- Attachment #2: Type: text/html, Size: 1902 bytes --]
next prev parent reply other threads:[~2015-02-13 9:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 7:46 Rich Felker
2015-02-13 9:29 ` Raphael Cohn [this message]
2015-02-13 9:38 ` Anthony J. Bentley
2015-02-13 9:50 ` Raphael Cohn
2015-02-13 9:57 ` Raphael Cohn
2015-02-13 10:45 ` Justin Cormack
2015-02-13 11:07 ` u-wsnj
2015-02-13 11:09 ` Justin Cormack
2015-02-13 13:02 ` Justin Cormack
2015-02-14 23:23 ` Felix Fietkau
2015-02-15 2:44 ` Rich Felker
2015-02-15 4:07 ` Isaac Dunham
2015-02-15 12:09 ` Sebastian Gottschall
2015-02-14 0:06 ` Isaac Dunham
2015-02-14 2:21 ` Rich Felker
2015-02-14 10:23 ` Justin Cormack
2015-02-14 20:35 ` Isaac Dunham
2015-02-14 2:23 ` 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='CACCP0GohXT5Vk+3Sc0hYajAsmaw_xOaLUhdV9xTcSy2=Tze+_w@mail.gmail.com' \
--to=raphael.cohn@stormmq.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).