| To: | Geert Uytterhoeven <geert@linux-m68k.org> |
|---|---|
| Subject: | Re: Questions? |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Thu, 7 Mar 2002 14:18:11 +0100 |
| Cc: | Marc Karasek <marc_karasek@ivivity.com>, Linux MIPS <linux-mips@oss.sgi.com> |
| In-reply-to: | <Pine.GSO.4.21.0203071410460.11036-100000@vervain.sonytel.be>; from geert@linux-m68k.org on Thu, Mar 07, 2002 at 02:11:50PM +0100 |
| References: | <20020307140754.A1817@dea.linux-mips.net> <Pine.GSO.4.21.0203071410460.11036-100000@vervain.sonytel.be> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Thu, Mar 07, 2002 at 02:11:50PM +0100, Geert Uytterhoeven wrote: > > The MIPS ABI only covers big endian systems - every "real" MIPS UNIX > > system is big endian. Everything else is a GNU extension. There is > > hardly any reason to choose a particular byteorder as usually endianess > > swapping takes so little CPU time that it isn't even meassurable but so > > I'm told there are exceptions. If portability of software you're > > going to write wrt. external data representation (disk or network) is > > of any importance then I suggest you use a system of the opposite > > endianess which trip problems much faster. > > I really like the last part! ;-) > > BTW, you forgot to mention to go for a full 64-bit port, to trip even more > problems faster :-) Fortunately in practice that hasn't been a minefield as big as you'd imagine. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Questions?, Geert Uytterhoeven |
|---|---|
| Next by Date: | Fwd: [e-users] software patents in Europe, Jay Konrad |
| Previous by Thread: | Re: Questions?, Geert Uytterhoeven |
| Next by Thread: | Re: Questions?, Richard Hodges |
| Indexes: | [Date] [Thread] [Top] [All Lists] |