Date: Thu, 15 Mar 2012 10:17:55 -0600 From: Warner Losh <imp@bsdimp.com> To: Juli Mallett <juli@clockworksquid.com> Cc: "freebsd-mips@FreeBSD.org" <freebsd-mips@FreeBSD.org> Subject: Re: Unbreaking ports with n64 MIPS. Message-ID: <E580AB5B-AD2A-4E04-A040-8E9E5D667040@bsdimp.com> In-Reply-To: <CACVs6=8z4BYcpQ=jVKLLb7v2LmSD-MRxXQdYRrOj-hG1j572Cg@mail.gmail.com> References: <CACVs6=8z4BYcpQ=jVKLLb7v2LmSD-MRxXQdYRrOj-hG1j572Cg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Juli,
I'd be fine with mips64 and mips64eb being the same, and moving from the =
former to the latter as the uname reported value. I almost did it when I =
was doing the stuff, but the pedants were against me and I didn't have =
any good amo to push back at them. This would be a good reason. The =
code was a little simpler when I always specified the eb on the end for =
all mips ports, so there's some tricks in the tree to keep expressions =
from getting too gross you'll have to watch out for.
As for IRIX, n32 binaries were run on it, but there never was a n32 =
kernel that I recall. It was just a funky ABI that you could compile =
your programs to if they had problems with the n64 ABI. So the OS =
didn't report anything special there. Our notion of an n32 kernel is =
historically a bit funkadelic.
Warner
On Mar 15, 2012, at 1:46 AM, Juli Mallett wrote:
> All,
>=20
> Does anyone object to changing the target name of mips64eb to be
> rendered as mips64? It's difficult to build ports because although
> the redundant "mipseb" as widely-recognized as synonymous as "mips",
> our quirky use of "mips64eb" instead of "mips64" just plain breaks
> stuff. "mips64el" is, of course, recognized, but it's generally
> assumed that MIPS is big-endian by default. I understand this
> assumption wasn't made in FreeBSD because the port that was committed
> focused early on a number of little-endian MIPS systems, but it seems
> worthwhile to switch. I'm happy to make the relevant changes.
>=20
> Thanks,
> Juli.
>=20
> PS: This may only need to be changed in how we name things in our GCC
> and binutils to fix ports, but I'd rather change everything else to
> match for the sake of consistency.
>=20
> PPS: What to do for n32? I think mips64{,el} is right for GCC and
> binutils, with something like "n32" in the OS name, but I haven't
> booted IRIX in almost a decade, so I can't remember what the
> convention is. I don't even know if there's software in ports that
> would care.
> _______________________________________________
> freebsd-mips@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-mips
> To unsubscribe, send any mail to =
"freebsd-mips-unsubscribe@freebsd.org"
>=20
>=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E580AB5B-AD2A-4E04-A040-8E9E5D667040>