Sponsored Content
Full Discussion: AIX endian again
Top Forums UNIX for Advanced & Expert Users AIX endian again Post 17923 by Perderabo on Thursday 21st of March 2002 08:16:30 AM
Old 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

Endian issues in TCP/IP

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

Big and Little Endian

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

Endian Conversion

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

Little Endiean and Big Endian

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

Migrating Oracle from Big Endian to Little Endian Platorm

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

question about the little-endian in sparc

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

Endian vs pfsense??

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
ENDIAN(3)						     Linux Programmer's Manual							 ENDIAN(3)

NAME
htobe16, htole16, be16toh, le16toh, htobe32, htole32, be32toh, le32toh, htobe64, htole64, be64toh, le64toh - convert values between host and big-/little-endian byte order SYNOPSIS
#define _BSD_SOURCE #include <endian.h> uint16_t htobe16(uint16_t host_16bits); uint16_t htole16(uint16_t host_16bits); uint16_t be16toh(uint16_t big_endian_16bits); uint16_t le16toh(uint16_t little_endian_16bits); uint32_t htobe32(uint32_t host_32bits); uint32_t htole32(uint32_t host_32bits); uint32_t be32toh(uint32_t big_endian_32bits); uint32_t le32toh(uint32_t little_endian_32bits); uint64_t htobe64(uint64_t host_64bits); uint64_t htole64(uint64_t host_64bits); uint64_t be64toh(uint64_t big_endian_64bits); uint64_t le64toh(uint64_t little_endian_64bits); DESCRIPTION
These functions convert the byte encoding of integer values from the byte order that the current CPU (the "host") uses, to and from little- endian and big-endian byte order. The number, nn, in the name of each function indicates the size of integer handled by the function, either 16, 32, or 64 bits. The functions with names of the form "htobenn" convert from host byte order to big-endian order. The functions with names of the form "htolenn" convert from host byte order to little-endian order. The functions with names of the form "benntoh" convert from big-endian order to host byte order. The functions with names of the form "lenntoh" convert from little-endian order to host byte order. VERSIONS
These function were added to glibc in version 2.9. CONFORMING TO
These functions are nonstandard. Similar functions are present on the BSDs, where the required header file is <sys/endian.h> instead of <endian.h>. Unfortunately, NetBSD, FreeBSD, and glibc haven't followed the original OpenBSD naming convention for these functions, whereby the nn component always appears at the end of the function name (thus, for example, in NetBSD, FreeBSD, and glibc, the equivalent of OpenB- SDs "betoh32" is "be32toh"). NOTES
These functions are similar to the older byteorder(3) family of functions. For example, be32toh() is identical to ntohl(). The advantage of the byteorder(3) functions is that they are standard functions available on all Unix systems. On the other hand, the fact that they were designed for use in the context of TCP/IP means that they lack the 64-bit and little-endian variants described in this page. EXAMPLE
The program below display the results of converting an integer from host byte order to both little-endian and big-endian byte order. Since host byte order is either little-endian or big-endian, only one of these conversions will have an effect. When we run this program on a little-endian system such as x86-32, we see the following: $ ./a.out x.u32 = 0x44332211 htole32(x.u32) = 0x44332211 htobe32(x.u32) = 0x11223344 Program source #include <endian.h> #include <stdint.h> #include <stdio.h> #include <stdlib.h> int main(int argc, char *argv[]) { union { uint32_t u32; uint8_t arr[4]; } x; x.arr[0] = 0x11; /* Lowest-address byte */ x.arr[1] = 0x22; x.arr[2] = 0x33; x.arr[3] = 0x44; /* Highest-address byte */ printf("x.u32 = 0x%x ", x.u32); printf("htole32(x.u32) = 0x%x ", htole32(x.u32)); printf("htobe32(x.u32) = 0x%x ", htobe32(x.u32)); exit(EXIT_SUCCESS); } SEE ALSO
byteorder(3) COLOPHON
This page is part of release 3.25 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. GNU
2009-01-19 ENDIAN(3)
All times are GMT -4. The time now is 02:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy