From owner-freebsd-mips@FreeBSD.ORG Thu Mar 15 16:22:15 2012 Return-Path: Delivered-To: freebsd-mips@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D1849106566C for ; Thu, 15 Mar 2012 16:22:15 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 6E37D8FC15 for ; Thu, 15 Mar 2012 16:22:15 +0000 (UTC) Received: from [10.30.101.53] ([209.117.142.2]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id q2FGI0Fv060611 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Thu, 15 Mar 2012 10:18:02 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Thu, 15 Mar 2012 10:17:55 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Juli Mallett X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Thu, 15 Mar 2012 10:18:02 -0600 (MDT) Cc: "freebsd-mips@FreeBSD.org" Subject: Re: Unbreaking ports with n64 MIPS. X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 16:22:15 -0000 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