From: John Spencer <maillist-musl@barfooze.de>
To: musl@lists.openwall.com
Subject: roadmap for 0.9.8 ?
Date: Thu, 01 Nov 2012 00:37:27 +0100 [thread overview]
Message-ID: <5091B637.3060107@barfooze.de> (raw)
i was thinking about what will go into the next release...
open positions that were originally intended to go into 0.9.7 are, as
taken from the latest "pending for release" mails:
- dl_iterate_phdr() - looks as if this is currently cooking, and
possibly an important bit to improve libgcc support,
- explicit mips soft-float abi support (mainly for use with broken
openwrt kernels) ,
- wordexp ?
- subarchs in build system (e.g. mips-softfloat, arm-hardfloat, etc.),
- nsz' suggested math improvements ?
additionally, i think it'd make sense to add stubs for the missing
optional schedule functions (as most of them are already there), that
way we could build some exotic programs like "fluidsynth" without
patches, and further increase the pkgsrc success rate:
posix_spawnattr_setschedparam
posix_spawnattr_setschedpolicy
posix_spawnattr_getschedparam
posix_spawnattr_getschedpolicy
pthread_attr_getinheritsched
pthread_attr_getschedpolicy
pthread_attr_setinheritsched
pthread_attr_setschedpolicy
pthread_getschedparam
pthread_mutex_getprioceiling
pthread_mutex_setprioceiling
pthread_mutexattr_getprioceiling
pthread_mutexattr_getprotocol
pthread_mutexattr_setprioceiling
pthread_mutexattr_setprotocol
pthread_setschedparam
pthread_setschedprio
pthread_getschedprio
(i hope that's complete)
- ppc port ?
is there something else i missed, and what are your plans ?
besides of musl itself, i think it would be a nice achievement if we
could get the microblaze toolchain patches integrated in the upstream
repos (or at least patches against current gcc/binutils trees), so that
we distro-builders dont need to special-case for microblaze.
next reply other threads:[~2012-10-31 23:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 23:37 John Spencer [this message]
2012-11-01 0:05 ` Rich Felker
2012-11-08 22:24 ` Rich Felker
2012-11-09 15:36 ` John Spencer
2012-11-09 18:51 ` 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=5091B637.3060107@barfooze.de \
--to=maillist-musl@barfooze.de \
--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).