Xref: utzoo comp.arch:8065 comp.misc:4850 comp.lang.misc:2639 comp.protocols.misc:483
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!xanth!mcnc!ncsuvx!ece-csc!ncrcae!ncrlnk!ncrwic!encad!enlog!mclauss
From: mclauss@enlog.Wichita.NCR.COM (Mark Clauss)
Newsgroups: comp.arch,comp.misc,comp.lang.misc,comp.protocols.misc
Subject: Re: Unification of big and little endian architectures.
Keywords: dump little-endian strings
Message-ID: <324@enlog.Wichita.NCR.COM>
Date: 30 Jan 89 06:36:25 GMT
References: <170@microsoft.UUCP> <4008@hubcap.UUCP> <482@babbage.acc.virginia.edu> <7193@csli.STANFORD.EDU> <1371@X.UUCP> <5462@pdn.nm.paradyne.com>
Reply-To: mclauss@enlog.UUCP (Mark Clauss)
Organization: NCR Corporation, Wichita, Kansas
Lines: 20

In article <5462@pdn.nm.paradyne.com> alan@pdn.nm.paradyne.com (0000-Alan Lovejoy) writes:
>It would be better to provide load and store operations that are
>specifically big or little endian:
>
>LLE.W -- load little endian word
>......

This would require a large field in the coding of these instructions. Are
these bits available for use? Maybe this is a real good idea when we go 
to 64 bit instructions. There are other ways to do this (ie. an "endian"
bit in a configuration register) but they aren't very RISCY.

Now that I think of it 64 bit instructions aren't very RISCY either.


-- 
Mark Clauss  Hardware Engineering, NCR Wichita <Mark.Clauss@Wichita.NCR.COM>
 NCR:654-8120                              <{uunet}!ncrlnk!
(316)636-8120         <{ece-csc,hubcap,gould,rtech}!ncrcae!ncrwic!mark.clauss>
           <{sdcsvax,cbatt,dcdwest,nosc.ARPA,ihnp4}!ncr-sd!