From: James MacDonald Newsgroups: comp.os.msdos.djgpp Subject: Re: FreeWin95 Project Date: Wed, 11 Jun 1997 16:45:10 +0100 Organization: Trills and Technologies Distribution: world Message-ID: References: <5n32mq$sj1 AT freenet-news DOT carleton DOT ca> NNTP-Posting-Host: netbook.demon.co.uk MIME-Version: 1.0 Lines: 37 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk In article , "Art S. Kagel" scribbled : >On 4 Jun 1997, Paul Derbyshire wrote: > >> >> Josef Moellers (mollers DOT pad AT sni DOT de) writes: >> > I beg to differ. >> > It's the processor hardware that determines the endianness. The OS has >> > to live with it or ... die. >> >> As long as the CPU isn't bytesexual, yep. >> >> > There are CPUs that can be both, e.g. the MIPS CPUs can switch between >> > big endian and little endian mode. >> >> Those are called "bytesexual". There're a few like that. Not all Unices >> run on bytesexual machines. (In fact a unix of some kind or other can be >Actually I've been told be people who should know that the Pentium and >Pentium Pros have an Endian switch just like the MIPS processors, though >I do not know of anyone who is using it. Indeed at Bloomberg we have >much BigEnd dependent code (legacy from old Perkin-Elmer CPUs which >survived well on Data General's M88110 Aviion systems). We must now move >to an Intel platform and DG has produced compilers and OS drivers to >support our code WITHOUT switching the CPU to BigEndian mode as they are >not willing to port DGUX/Intel to the Pentium in BigEndian mode. So it >IS possible to run BigEndian on a Little Endian machine. So far the only >performance problems not yet licked involve floating point data and DG >has just started working on that. Another example is the ARM 610, as used in the RiscPC - this can be big or little endian. -- Revised anti-spam in use : remove X to reply - 'Xnetbook' becomes 'netbook' Anti-spam thermonuclear warheads cheap at only $300!