From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Open/pending issues as of Jan 17
Date: Mon, 18 Jan 2016 12:25:30 +0100 [thread overview]
Message-ID: <20160118112530.GB9621@port70.net> (raw)
In-Reply-To: <20160117231554.GA19126@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2016-01-17 18:15:54 -0500]:
> With a quick review of the mailing list since late November I found
> the following possibly-open issues:
>
> - resolver search domain support
> - preinit_array
> - mlock2 syscall wrapper
> - mips siginfo_t fix
i think this should have priority
(abi visible bug, should not wait for arch/bits cleanup)
> - avl tree: any changes still pending??
there are no known bugs in the current code, but
tsearch_small.c would be an improvement over it.
(and twalk,tfind should be separate tu)
> - adding pot file for translators
> - unsetenv pointer eval after free
> - printf big widths/precisions
> - atomic.h overhaul
> - dirent.h macros
> - dlopen deadlock
> - setvbuf
random stuff:
- linux 4.* uapi (includes mlock2, but a lot of other stuff too)
- symbol versioning (for at least gcc-6 libgcc_s.so)
- __cxa_thread_atexit_impl ? (i expect this to come up in real code)
- stdatomic.h
- string functions correctness
- regex bre extensions \+ \? \|
- regcomp increase tre_stack_new limit
- str{f,p}time %z %Z %k %l ?
- noreturn __assert_fail ?
- hidden visibility for internal functions
- compiler builtins in libc (sqrt, fabs, memcpy..)
- asm -> inline asm
- ld128 math
> Also, not code issues, but the following possibly-open documentation
> issues were found:
>
> - documenting atomic.h primitives contracts
> - documenting "known UB" in musl
>
> There were a few other patches that were mostly trivial which I just
> committed outright, and the big one, out-of-tree builds, that I
> finally committed after some more testing.
>
> Is there anything else I missed that's an open issue right now? Or
> requests for prioritizing the above list? I'm going to try to take the
> above (and anything else that comes up) and turn it into a plan for
> what can reasonably go into the next release.
>
> Rich
next prev parent reply other threads:[~2016-01-18 11:25 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 [this message]
2016-01-29 2:34 ` Rich Felker
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=20160118112530.GB9621@port70.net \
--to=nsz@port70.net \
--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).