Is the code Endian neutral?

代码是否和字节顺序有关？

Most RISC processors are big-endian.

大多数RISC处理器都是big - endian。

Generate "big endian" format output.

生成“大端”格式输出。

Generate "little endian" format output.

生成“小端”格式输出。

Byte order: big endian or little endian.

字节次序：大尾数法还是小尾数法。

Listing 2. Big endian vs. little endian.

清单2 . big endian与little endian。

Intel microprocessors are little-endian.

intel微处理器是little - endian。

All processors of the Intel x86 family are little endian.

所有Intel x86家族的处理器使用的都是小端字节。

UTF-16BE: 16-bit UCS Transformation format, big-endian byte order.

UTF - 16 BE： 16位UCS转换格式，大尾数法字节顺序。

We have bit fields in C and C + + that help to deal with endian issues.

在c和c+ +中有位域来帮助处理endian的问题。

The example that caught us was compiling PINE on a big-endian system.

我们要使用的例子是在一个高位优先系统上编译PINE。

UTF-16LE: 16-bit UCS Transformation format, little-endian byte order.

UTF - 16le： 16位UCS转换格式，小尾数法字节顺序。

For instance, PNG documents (a competitor to TIFF) are always big endian.

例如，PNG文档(TIFF的一个竞争者)始终使用大尾数法。

However, on a little endian machine, the word 0x12345678 will be laid out as follows.

然而，在little endian机器上，字0x12345678的布局如下所示。

For example, the 32-bit word 0x12345678 will be laid out on a big endian machine as follows

例如，32 位的字 0x12345678 在 big endian 机器上的布局如下

Big-endian means that the most significant byte has the lowest address (the word is stored big-end-first).

big - endian意味着最高位字节存储在最低地址(按高位优先的顺序存储字)。

The byte ordering (Big-Endian or Little-Endian) for a storage access is specified by the operating system.

存储器存取的字节顺序(Big - Endian或Little - Endian)是由操作系统指定的。

If an integer is four bytes in length with a big-endian encoding, then the message USES that same representation.

如果整数采用big - endian法编码、用四个字节表示，那么消息中也使用同样的表示。

Little-endian means that the least significant byte has the lowest address (the word is stored little-end-first).

而little - endian意味着最低位字节存储在最低地址(按低位优先的顺序存储字)。

Or, how are arguments transmitted between machines with different addressing schemes, big endian vs. little endian?

或者，变量如何在使用不同寻址方案(大尾数法，小尾数法)的机器间发送？

Big-endian and little-endian UTF-8 are identical, because UTF-8 is defined in terms of 8-bit bytes rather than 16-bit words.

UTF - 8用Big - endian和little - endian来表示都是一样的，因为UTF - 8是按8位字节而不是16位字定义的。

But what happens if a client running on a big endian IBM PowerPC attempts to send a 32-bit integer to a little endian Intel x86?

但是，如果一个运行在高位优先的IBM PowerPC上的客户端发送一个32位的整数到一个低位优先的Intel x86，那将会发生什么呢？

All three of these may or may not be preceded by a Unicode byte order mark in either UTF-8, big-endian UTF-16, or little-endian UTF-16.

所有这三行之前都可能有Unicode字节序标记，如utf - 8、big - endian UTF - 16或little - endian UTF - 16。

However, there is no standard set of functions for 64-bit. But Linux provides the following macros on both big and little endian systems.

然而，对于64位整数来说，并没有标准的函数集。

Except for the limitations described below, you can take a backup from any big-endian server and restore it to any other big-endian server.

除了以下限制外，可以为任何big - endian服务器做备份，然后将它恢复到另一个big - endian服务器。

This is one of the things that's available on a POWER5 that you can't do on a G5; you could, in theory, build your code for little-endian usage.

这是在POWER 5上可用但是在G5上无法使用的功能之一；理论上来说，您可以为低位优先的用法来构建自己的代码。

Unfortunately, the Linux distribution used doesn't provide corresponding little-endian libraries to link with, so you can't test little-endian code.

不幸的是，所使用的Linux发行版并没有提供对应的低位优先库来进行链接，因此就不能对低位优先测试。

Note: Depending on the platform and whether the mem structure is big endian or little endian, you may need to swap the order in which bytes are read.

注意：根据不同平台，以及 men 结构是大端字节序还是小端字节序，您可能需要交换读取字节的顺序。

One thing to do is look for a number whose range you can predict broadly, and just see what it comes out as when read both big-endian and little-endian.

要做的一件事是寻找一个预测范围很大的数字，看一下当读取高位优先和低位优先时到底是什么情况。

When students do these embedded experiments, they do often face the problem of the transformation between big-endian and little-endian about byte order.

学生在做嵌入式系统的实验时，经常会遇到字节顺序的大小端转化问题。