mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Proposed roadmap to 1.0
Date: Sun, 30 Jun 2013 01:34:09 -0400	[thread overview]
Message-ID: <20130630053408.GP29800@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130630052045.GB1368@newbook>

On Sat, Jun 29, 2013 at 10:20:45PM -0700, Isaac wrote:
> > 1.0.0
> > Projected release: Early fall
> > Key targets:
> > - Polished documentation.
> > - Organized and coordinated publicity plan.
> > - At least one new exciting addition to make the release noteworthy,
> >   but which has no chance of breaking things that work. Best candidate
> >   would be one or more new ports, labeled experimental.
> 
> How about s390 and ia64? ;-)

s390 looks like a maybe. I'm not sufficiently familiar with it to call
it a no, and Rob seemed interested in supporting it at one time.

ia64 is nothing but gratuitous incompatibility and arch-specific code
where it doesn't belong, all for an arch that was dead before it was
launched. I think it's officially dead now even, or maybe that's just
wishful thinking.

> All joking aside, I'd say +1. 
> And for ports, arm64, mips64 or mips n32, x32, and/or sh seem like
> interesting targets. 

Agreed, all of those look interesting. Super H might be another
candidate; IIRC it was used on some game consoles and automotive
control computers.

> While sparc is not "dead", basically leon is the only sparc cpu that is 
> alive and likely to provide an interested audience.
> And that's sparc32.

I don't really know much about sparc except that the register windows
system looks ugly.

> m68k/coldfire are 32-bit only, slow, and largely obsolete with little 
> prospect of new development (Freescale is working on ppc and arm systems),
> but there is some use of them in the embedded market, so I could imagine a
> port being useful to someone.

m68k is in some ways an arch I'd like to avoid, but if it's
interesting to people we could do it.

> Do we currently support 64-bit ppc?

No, but 32-bit apps can run on 64-bit kernel as far as I know. I was
just looking at the 64-bit ABI earlier today and it's rather
gratuitously ugly, but probably not too hard to support.

> ia64 appears to be limited in use/dying, besides not being the ideal target.
> (big iron, and you'd pretty much need to interest Oracle and similar companies
> before you get much use).
> hppa and alpha are most interesting for a computer historian.

Is hppa the same as pa-risc? If so, it's one I'd definitely like to
omit. It's the only machine with a stack that grows upward, so it's a
good deal of added generality required for just one arch. And of
course like you say it's of interest only to historians.

Alpha was kind of interesting, but it's just as dead I think... If I
remember right, the kernel support was broken for years and nobody
realized...

> m32r is live, but I'm not aware of much interest.
> tilera and epiphany (the Parallela coprocessor) sound interesting,
> but are likely to be limited in availability.

Not familiar with them, but my guess would be they're interesting. In
embedded, everything has niche uses. On the high-end server side, on
the other hand, anything but x86_64 (for straight power) or ARM (for
cutting the primary cost of a data center: electricity) is madness. In
other words, I think there's a lot more value in supporting diversity
on the embedded side than on the enterprise side.

Rich


  reply	other threads:[~2013-06-30  5:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-29 23:50 Rich Felker
2013-06-30  2:53 ` Rob Landley
2013-06-30  3:01   ` Rich Felker
2013-06-30  5:20 ` Isaac
2013-06-30  5:34   ` Rich Felker [this message]
2013-06-30  6:42     ` Isaac
2013-06-30  7:21       ` Justin Cormack
2013-06-30 12:02         ` Rich Felker
2013-07-04 18:13         ` Rob Landley
2013-07-07 20:25           ` Isaac
2013-07-04 18:10       ` Rob Landley
2013-07-07 20:30         ` Isaac
2013-06-30  9:24     ` Rob Landley
2013-06-30 10:45     ` Szabolcs Nagy
2013-06-30 21:29       ` Luca Barbato
2013-07-05 15:12   ` Rob Landley
2013-06-30  5:49 ` Strake
2013-07-17 16:02 ` Rich Felker
2013-07-24 18:36   ` Rob Landley
2013-07-24 19:47     ` Rich Felker
2013-07-25  7:25       ` Daniel Cegiełka
2013-07-25  7:40         ` Rich Felker
2013-07-27  5:30       ` Rob Landley
2013-07-25 10:29     ` Timo Teras
2013-07-24 14:14 ` orc
2013-07-24 14:42   ` Rich Felker
2013-07-24 15:29     ` orc
2013-07-24 16:04       ` Rich Felker
2013-07-24 16:25         ` orc
2013-07-24 19:41           ` 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=20130630053408.GP29800@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).