mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Thinking about release
Date: Wed, 12 Jun 2013 21:25:17 -0400	[thread overview]
Message-ID: <20130613012517.GA5859@brightrain.aerifal.cx> (raw)

Hi all,

It's been mentioned that we're overdue for a release, and it looks
like we have a fair amount of new stuff since the last release. Major
changes so far:

- Accepting \n in dynamic linker path file
- Fixed broken x86_64 sigsetjmp
- Removed wrong C++ __STDC_*_MACROS checks
- Thread exit synchronization issues
- Conforming overflow behavior in clock()
- Support for large device numbers
- Math optimizations on i386
- C11 float.h macro additions
- Fixes for exceptions in fma (gcc bug workarounds)
- Fix misaligned stack when running ctors/dtors
- Support for %m modifier in scanf
- Support for using gcc intrinsic headers with musl-gcc wrapper
- PRNG fixes
- Per-process and per-thread cputime clocks and new(ish) Linux clocks

I think the ether.h functions could definitely still make it in for
this release too. inet_makeaddr, etc. could probably also be merged.
Most of the other major items left on the agenda since the last
release are probably not going to happen right away unless there's a
volunteer to do them (zoneinfo, cpuset/affinity, string functions
cleanup, C++ ABI matching, ARM-optimized memcpy) and one, the ld.so
symlink direction issue, still requires some serious discussion and
decision-making.

If anyone else has input for what should still go into the next
release, please jump in and discuss.

Rich


             reply	other threads:[~2013-06-13  1:25 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13  1:25 Rich Felker [this message]
2013-06-13  1:33 ` Andre Renaud
2013-06-13  1:43   ` Rich Felker
2013-07-09  5:06     ` Andre Renaud
2013-07-09  5:37       ` Rich Felker
2013-07-09  6:24         ` Harald Becker
2013-07-09 21:28         ` Andre Renaud
2013-07-09 22:26           ` Andre Renaud
2013-07-10  6:42             ` Jens Gustedt
2013-07-10  7:50               ` Rich Felker
2013-07-10 22:44             ` Andre Renaud
2013-07-11  3:37               ` Rich Felker
2013-07-11  4:04                 ` Andre Renaud
2013-07-11  5:10                   ` Andre Renaud
2013-07-11 12:46                     ` Rich Felker
2013-07-11 22:34                       ` Andre Renaud
2013-07-12  3:16                         ` Rich Felker
2013-07-12  3:36                           ` Andre Renaud
2013-07-12  4:16                             ` Rich Felker
2013-07-24  1:34                               ` Andre Renaud
2013-07-24  3:48                                 ` Rich Felker
2013-07-24  4:40                                   ` Andre Renaud
2013-07-28  8:09                                     ` Rich Felker
2013-07-11  5:27                 ` Daniel Cegiełka
2013-07-11 12:49                   ` Rich Felker
2013-07-15  4:25                 ` Rob Landley
2013-07-10 19:42           ` Rich Felker
2013-07-14  6:37             ` Rob Landley
2013-07-11  4:30           ` Strake
2013-07-11  4:33             ` Rich Felker
2013-07-10 19:38         ` Rob Landley
2013-07-10 20:34           ` Andre Renaud
2013-07-10 20:49             ` Nathan McSween
2013-07-10 21:01             ` Rich Felker
2013-06-13 15:46 ` Isaac
2013-06-26  1:44 ` Rich Felker
2013-06-26 10:19   ` Szabolcs Nagy
2013-06-26 14: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=20130613012517.GA5859@brightrain.aerifal.cx \
    --to=dalias@aerifal.cx \
    --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).