mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Short-term todo list - 18 Jul
Date: Sat, 19 Jul 2014 17:01:01 -0400	[thread overview]
Message-ID: <20140719210101.GD17402@brightrain.aerifal.cx> (raw)
In-Reply-To: <20140718051558.GA22286@brightrain.aerifal.cx>

On Fri, Jul 18, 2014 at 01:15:58AM -0400, Rich Felker wrote:
> Aside from the big development items left in this release cycle
> (adding locale functionality and IDN), there are a few more short-term
> tasks I want to get done in the next day or two based on open mailing
> list threads and other discussions. The ones I'm aware of right now
> are:
> 
> - Merging or1k

Done.

> - Finishing discussion of issetugid and hopefully merging

Discussion done. Just want to make a good commit message explaining
the rationale and I think it's ready to commit.

> - Reviewing glob_pattern_p patch

Done. Does anyone object to adding this or think it should be done
differently if added?

> - Figuring out what to do with atomic asm constaints & volatile

Almost done. I still want to add __volatile__ to all the archs that
are missing it and add the memory constraints for microblaze.

Also a_store seems to be broken on a number of archs... I'm trying to
figure out what to do with this too.

> - Fixing microblaze stat structure (& getting qemu fixed?)

Done. (Minus getting qemu fixed; anyone willing to volunteer to follow
up on that?)

> - Addressing mips stat structure dev_t endianness issue

I think this should be hidden away in arch/mips/syscall_arch.h but the
way the macros are done makes it ugly and difficult to add. I might
just flatten all the __syscallN functions.

Rich


  parent reply	other threads:[~2014-07-19 21:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18  5:15 Rich Felker
2014-07-18  7:31 ` Szabolcs Nagy
2014-07-19 21:01 ` Rich Felker [this message]
2014-07-20  1:50   ` Rich Felker
2014-07-20  5:43     ` 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=20140719210101.GD17402@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).