Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 21 Jun 2014 23:37:46 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Remaining roadmap targets for 1.1.3

On Fri, Jun 20, 2014 at 12:40:32AM -0400, Rich Felker wrote:
> Here are the not-yet-done primary targets from the roadmap:
> 
> - Resolver: IDN and result sorting.

Result sorting is done, modulo any potential bugs. Please test if you
can. In typical usage, IPv6 results (whether from /etc/hosts or DNS)
should be showing up last if you have an IPv4-only setup or if the
only IPv6 route is over 6to4, and first if you have a real IPv6 setup.
For results that are a mix of link-local or other differently-scoped
addresses the sorting is more complex. Testing with fancy IPv6 setups
would be very helpful.

> - Overhaul of if_nameindex and getifaddrs.

Still pending.

> - Merging fmtmsg. (I have reviewed it now though.)

Done.

> - Merging ports. (Probably not going to happen in this cycle.)

Indeed. or1k is mostly done, but probably not enough to think about a
merge yet, especially since it needs refitting for the reloc.h
changes. No idea on the status of aarch64.

> And secondary ones:
> 
> - Promoting x32 and sh from experimental.
> - Deduplicating header bits.
> - Private futex.

Let's punt on all these.

> And old items from the post-1.1.1 plans thread:
> - max_align_t

Still not sure what's best. Perhaps we should define max_align_t to
have alignment of MIN(8, alignof(long long), alignof(double),
alignof(long double)) or similar since that seems to be effectively
what GCC is doing. However I don't see any way to give the _type_ such
alignment without depending on GNU C. Per C11 I don't think _Alignas
is valid on struct/union members but I seem to remember hearing that
the committee is considering this a defect. Anyway, the whole topic is
probably still too complex to deal with between now and release.

> - __xmknod and __sysv_signal patch (ABI compat)

I just looked up the confusing mess with __xmknod taking a dev_t *
rather than dev_t, so I think I can knock this one off the list
between now and release.

> - sysconf(_SC_LINE_MAX) issue
> - errc-family functions
> - error.h
> - reallocarray
> - explicit_bzero

I think all of these should be deferred for now.

Rich

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.