From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3767 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Conformance issues to address after 0.9.12 release Date: Mon, 29 Jul 2013 02:34:56 -0400 Message-ID: <20130729063456.GA31564@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1375079709 32672 80.91.229.3 (29 Jul 2013 06:35:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Jul 2013 06:35:09 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3771-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jul 29 08:35:11 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1V3h31-0006Ju-DD for gllmg-musl@plane.gmane.org; Mon, 29 Jul 2013 08:35:11 +0200 Original-Received: (qmail 20295 invoked by uid 550); 29 Jul 2013 06:35:10 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 20287 invoked from network); 29 Jul 2013 06:35:09 -0000 Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3767 Archived-At: Here are a few issues I'd like to move to the agenda for after release: - strftime (and wcsftime) does not support the POSIX-2008 field width specifiers and 0/+ flags. This is fairly invasive in strftime, which was originally written to ISO C and the previous issue of POSIX, both of which have fixed field widths. It also requires a partial redesign of wcsftime. - i387 math asm does not truncate excess precision. Whether or not this omission is conforming in terms of the return value, it results in lost underflow exceptions, as demonstrated by nsz's math tests. As far as I know, these are the only open conformance issues except for the C locale issues, which will probably be resolved post-1.0, and documentation. The rest of the remaining roadmap items are nonstandard features and quality-of-implementation issues. Rich