[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150214022150.GI23507@brightrain.aerifal.cx>
Date: Fri, 13 Feb 2015 21:21:50 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: What would make musl 1.2?
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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
