mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Isaac Dunham <idunham@lavabit.com>
To: musl@lists.openwall.com
Subject: Re: musl 0.9.8 released
Date: Tue, 27 Nov 2012 18:43:29 -0800	[thread overview]
Message-ID: <20121127184329.a20d1160.idunham@lavabit.com> (raw)
In-Reply-To: <20121127024958.GA23123@brightrain.aerifal.cx>

On Mon, 26 Nov 2012 21:49:58 -0500
Rich Felker <dalias@aerifal.cx> wrote:

> 
> Release announcement for musl 0.9.8:
> 
>     New PowerPC port and major bug fixes and improvements for the MIPS
>     port. Coverage for more optional parts of POSIX including the
>     thread priority scheduling option and stubs for unsupported
>     functionality. Dynamic linker dl_iterate_phdr support. Various
>     minor bugs and strict conformance issues have also been fixed and
>     application compatibility improved.
Thanks!
> 
>     http://www.musl-libc.org/releases/musl-0.9.8.tar.gz

Mirrored at github.com/idunham/musl branch "master"

> As a post-release agenda, I'd like to first address things that have
> been in demand lately:
> 
> - Proper MIPS softfloat support
> - x32 port
> - ether.h interfaces
> - %m modifier for scanf
> - Affinity/cpuset stuff
> 
> And I have a few agenda items of my own:
> 
> - Self-synchronized destruction of FILE streams (same issue all
>   synchronization objects have had with self-synchronized
>   destruction -- unlocking thread may not access memory after the
>   destroying thread already got the lock).
> - Making stdio functions cancellable while waiting for locks.
> - Getting strace & gdb working properly with minimal patching.
> 
> That's about it..hopefully the next release cycle won't take so long.
> 
> Rich

All very good, and I don't think I've got any more to add...

So I guess that leaves the subarches like so:
x86:  i486, x86_64
arm:  arm(eb), armel
mips: mips(32), mipsel(32)
microblaze: microblaze
(What's the status of microblazeel/microblazele? configure looks not to recognize it...)
ppc:  powerpc(32)

Total arches:
6
Total subarches (distinct ABIs):
8-10 (depending on status of microblazeel and ABI compatability of armhf with armel)

-planned subarches: mipsel32-sf, mips32-sf
-planned arches: x32
-distant: mips64, mipsel64, ppc64 (I *think* Rich Pennington got these working, but they haven't been merged)
-unsupported subarches: i386

It seems Debian's using aarch64-* for ARMv8.

-- 
Isaac Dunham <idunham@lavabit.com>



  parent reply	other threads:[~2012-11-28  2:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-27  2:49 Rich Felker
2012-11-27 11:31 ` Szabolcs Nagy
2012-11-27 14:46   ` Rich Felker
2012-11-28  2:43 ` Isaac Dunham [this message]
2012-11-28  3:39   ` Rich Felker
2012-11-28  4:51     ` Isaac Dunham
2012-11-28 13:05       ` Rich Felker
2012-11-28 21:35         ` Rob Landley
2012-11-28 23:53           ` Rich Felker
2012-11-29  0:52             ` Rob Landley
2012-12-03 13:11 ` Szabolcs Nagy
2012-12-03 17:30   ` Rich Felker
2012-12-03 22:03     ` Szabolcs Nagy

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=20121127184329.a20d1160.idunham@lavabit.com \
    --to=idunham@lavabit.com \
    --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).