From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Remaining tasks for 1.1.4 release as of Jul 26
Date: Sun, 27 Jul 2014 22:32:18 -0400 [thread overview]
Message-ID: <20140728023218.GG4038@brightrain.aerifal.cx> (raw)
In-Reply-To: <20140726201448.GA14805@brightrain.aerifal.cx>
On Sat, Jul 26, 2014 at 04:14:48PM -0400, Rich Felker wrote:
> Here are the only major things I see left for the 1.1.4 release:
>
> - Adding non-dummy gettext functions
This is "done", but there are some additional features I'd like to get
in before the release: $LANGUAGE support and perhaps plurals. nsz
mentioned on IRC possibly writing an expression evaluator for this but
I don't know the timeframe.
> - Finish reviewing and merging if_nameindex/getaddrinfo patch
I've sent my remaining comments on this to the list. I'd like it if we
could get this smaller/simpler but I don't see any good way.
> - Fixing misplaced/missing barriers for SuperH atomic asm
Done. This code still has a number of issues I'd like to clean up, but
at least it should be safe now. In the long term I'd like to use a
similar strategy for both ARM and sh (and any other archs where the
atomic implementation needs to be selected at runtime) to minimize
both the code size/register spillage in the caller and the run time in
the callee.
> - Merging some remaining atomic asm fixups I have in progress
I've done the cleanup of cruft. I want to change some constraints to
be more consistent and add volatile attributes, but it's enough work
and enough chance to mess things up that I think I'll punt on the rest
for now and revisit it later.
> - Reviewing and merging getopt_long abbreviated options patch
I'm looking into a simpler approach to this that avoids the problem of
matching ambiguous abbreviations.
Rich
prev parent reply other threads:[~2014-07-28 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 20:14 Rich Felker
2014-07-28 2:32 ` Rich Felker [this message]
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=20140728023218.GG4038@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).