03-21-2002
Endian-ness in a cpu arises because we need to specify multi-byte integers with a byte address.
In the '60's I worked on an IBM 1130. It was a 16 bit machine and had no byte addressing. Address 0 was a 16 bit word. Address 1 was the next 16 bit word. There is no way to determine an endian-ness on a system like this.
I have never heard of any cpu that even allows bit addressing. If there was one, and if it required the programmer to specify a bit address for a byte, then we would need to worry about the endian-ness of a single byte.
The only time that byte endian-ness becomes apparent is when a byte is transmitted across a serial data line. TCP/IP is an example of this, and in TCP/IP, bytes are big-endian. (or more accurately, octets are big-endian, since TCP/IP does not assume that bytes are 8 bits). Contrary to your comment, this is what I regard as "normal". Most other serial protocols are also big-endian, at least most of the modern ones are.
On the other hand, RS-232 is little-endian. So is the old current-loop interface. The earlier teletype protocols are before my time, but I think that they were little-endian (but I'm not sure). These protocols never need to transit a multi-byte integer and they need to support both 7 bit and 8 bit characters.
So unless you are designing an i/o card to transmit bytes in a bit serial fashion, you can safely ignore this issue with every cpu that I have heard of.
But it's hard to be sure that something doesn't exist, so if someone out there knows about a cpu that requires a bit address for addressing its bytes, I would be very interested in the details of it.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
Can anybody tell me whether the little endian-big endian issues will affect porting from True64 to HP UNIX or TCP/IP will take care of that? If it affects what can be the solution.
Thank you, (3 Replies)
Discussion started by: informshilpa
3 Replies
2. Programming
We are developing an application using TLI for network communication.The Server Code is developed in Sun and client in SCO unix. When we route data from Client to Server we encrypt the data using DES algotithm utility.The problem we are facing that Sun uses Big Endian methodology to store data in... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies
3. UNIX for Advanced & Expert Users
Hi everybody,
I met this week a problem.
For now, we used TRU64 system based on alpha. Now, we're installing UP-UX systems (on Itanium). And we have problem with our files. Indeed, we use file with COMP-3, COMP-5 data. These files are used on both platforms. (we use also TXT files which... (1 Reply)
Discussion started by: bigmike59270
1 Replies
4. UNIX for Dummies Questions & Answers
Dear Friends,
I have one question in my mind. That question is
"how to detect whether the system is little endiean or big endian"
Processing the bit position is the difference between this endians.
But I could not understand how to find the pariticular sytem works... (3 Replies)
Discussion started by: Nirmal Babu
3 Replies
5. UNIX and Linux Applications
Hi,
We are trying to migrate an oracle database from Sun Solaris (SunOS 5.9 Generic_118558-28 sun4u sparc SUNW,Ultra-60) to Linux 2.6.18-53.1.19.el5 #1 SMP Tue Apr 22 03:01:10 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux which is basically a Big Endian to Little Endian conversion.
We shutdown... (3 Replies)
Discussion started by: luft
3 Replies
6. Solaris
hi folks, in the sparc v9 manul , it says it is possible to access the memory data in little-endian mode, but there is only privilaged instruction that could set the PSTATE ( the cle bit ) regist. if I'm in the user mode , is it possible for me to access the data in little-endian mode? (10 Replies)
Discussion started by: zerocool_08
10 Replies
7. UNIX and Linux Applications
Hi
Endian firewall free version if we do compare pfsense
For a LAN network with active user 1000
Which do you recommend
Share (0 Replies)
Discussion started by: mnnn
0 Replies
LEARN ABOUT DEBIAN
tslmendian
TSLMENDIAN(1) User Contributed Perl Documentation TSLMENDIAN(1)
NAME
tslmendian - change the byte-order of sunpinyin's threaded back-off language model
SYNOPSIS
tslmendian [option]
DESCRIPTION
slmendian converts the binary language model files used by SunPinyin from big-endian to small-endian or vice versa.
OPTIONS
-e endian
Specify the output-lm-file's endian-ness. It can be le or ge. If not given, tslmendian uses the host's endian-ness.
-v Prints out the endian-ness of input-lm-file.
-i input-lm-file
Identify the input file of convert. Generally, this file is generated by slmthread or tslmpack.
-o out-lm-file
Identify the output file of convert.
NOTES
The converted output file is equivalent to the input. But if you compare the output of tslminfo of both files, the ARPA file generated by
tslminfo may different. This is due to the different precision in different machines.
And due to uninitialized padding data in data structure, the checksum of the original data file may different from the converted-back file,
even though they are identical from SunPinyin's point of view.
AUTHOR
Originally written by Kov. Chai <tchaikov.gmail.com>. Currently maintained by Kov.Chai <tchaikov@gmail.com>.
SEE ALSO
slmthread(1). tslminfo, tslmpack.
perl v5.14.2 2012-06-09 TSLMENDIAN(1)