From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: What would make musl 1.2?
Date: Fri, 13 Feb 2015 21:21:50 -0500 [thread overview]
Message-ID: <20150214022150.GI23507@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150214000655.GB1452@newbook>
On Sat, Feb 14, 2015 at 12:06:56AM +0000, Isaac Dunham wrote:
> On Fri, Feb 13, 2015 at 11:09:55AM +0000, Justin Cormack wrote:
> > mips n32 - this seems to have mostly bypassed linux and android alas,
> > with only gentoo supporting it, despite the o32 ABI being horrible.
> > But Musl users should be encouraged to use n32 if building form
> > scratch...
>
> I've looked repeatedly, but everything I found has seemed to imply
> that n32 is like x32: a "32-bit" ABI that requires 64-bit hardware.
> Is this incorrect?
Yes, that's what it is. Interestingly they avoided some of the huge
mistakes of x32, but I think that was largely a consequence of having
most or all of the kernel n32 types match the plain 32-bit types
(sadly including, if I'm not mistaken, 32-bit time_t) rather than
being a crazy mix. Someone who knows n32 better could probably clarify
this.
If I remember correctly, the Loongson mips64-based laptops use n32,
probably because mips is painfully underpowered for a laptop/desktop
even without doubling the memory bus pressure with 64-bit pointers.
Rich
next prev parent reply other threads:[~2015-02-14 2:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 7:46 Rich Felker
2015-02-13 9:29 ` Raphael Cohn
2015-02-13 9:38 ` Anthony J. Bentley
2015-02-13 9:50 ` Raphael Cohn
2015-02-13 9:57 ` Raphael Cohn
2015-02-13 10:45 ` Justin Cormack
2015-02-13 11:07 ` u-wsnj
2015-02-13 11:09 ` Justin Cormack
2015-02-13 13:02 ` Justin Cormack
2015-02-14 23:23 ` Felix Fietkau
2015-02-15 2:44 ` Rich Felker
2015-02-15 4:07 ` Isaac Dunham
2015-02-15 12:09 ` Sebastian Gottschall
2015-02-14 0:06 ` Isaac Dunham
2015-02-14 2:21 ` Rich Felker [this message]
2015-02-14 10:23 ` Justin Cormack
2015-02-14 20:35 ` Isaac Dunham
2015-02-14 2:23 ` 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=20150214022150.GI23507@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).