From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Open/pending issues as of Jan 17
Date: Thu, 28 Jan 2016 21:34:45 -0500 [thread overview]
Message-ID: <20160129023444.GT238@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160118112530.GB9621@port70.net>
On Mon, Jan 18, 2016 at 12:25:30PM +0100, Szabolcs Nagy wrote:
> random stuff:
> - linux 4.* uapi (includes mlock2, but a lot of other stuff too)
Done.
> - symbol versioning (for at least gcc-6 libgcc_s.so)
This is a fairly invasive change and needs testing and possibly
further discussion. It's big enough I'd like to allocate it attention
on the roadmap for a specific release cycle. It's tentatively a
secondary target for the next cycle but we could move it up to primary
if this is becoming a serious problem.
> - __cxa_thread_atexit_impl ? (i expect this to come up in real code)
It looks to me like gcc emulates it with a pthread key to get a dtor
and doesn't actually need help from the libc. If so I don't think it
makes sense to bother with doing a better implementation on the libc
side unless/until we can resolve the lazy allocation bug in their ABI.
> - stdatomic.h
Let's look at this later.
> - string functions correctness
I don't think there's much that can be done aside from adding the
may_alias attribute. But at least that small improvement can go on the
agenda for the next release cycle.
> - regex bre extensions \+ \? \|
Possibly going to apply this now unless you see a risk of breaking
anything else.
> - regcomp increase tre_stack_new limit
Sounds ok to apply now but I lost track of where the patch is.
> - str{f,p}time %z %Z %k %l ?
> - noreturn __assert_fail ?
> - hidden visibility for internal functions
Let's look at these after release.
> - compiler builtins in libc (sqrt, fabs, memcpy..)
> - asm -> inline asm
A little bit of this was done (for arm) but I'd like to continue where
it makes sense.
> - ld128 math
Yes, that would be nice. Should we set a specific roadmap goal for
adding it or at least adding the most important stuff (like sqrtl)
that's currently badly broken.
Rich
next prev parent reply other threads:[~2016-01-29 2:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 23:15 Rich Felker
2016-01-18 11:25 ` Szabolcs Nagy
2016-01-29 2:34 ` Rich Felker [this message]
2016-01-18 12:12 ` Christian Neukirchen
2016-01-29 2:37 ` Rich Felker
2016-01-29 7:54 ` Natanael Copa
2016-01-29 18:19 ` Rich Felker
2016-02-19 10:30 ` netflix support (WAS: Open/pending issues as of Jan 17) Natanael Copa
2017-10-29 9:52 ` Open/pending issues as of Jan 17 Kurt H Maier
2016-01-19 1:14 ` Bobby Bingham
2016-01-19 1:16 ` Khem Raj
2016-01-29 2:21 ` 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=20160129023444.GT238@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).