big-endian

big-endian

美 　英

• 网络大端；大端字节序；大端模式

例句

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服务器。

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）是由操作系统指定的。

Note that networks usually use big-endian byte order, so an application running on System z does not need conversion here.

注意，网络通常使用大端字节顺序，因此在Systemz上运行的应用程序在这里不需要转换。

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

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

Defines the image internal characterset for JIS encoded user comments if image is in motorola byte order (big-endian).

定义了JIS编码的用户注释的图像内部字符集，如果图像是摩托罗拉字节顺序（big-endian）的话。

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

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

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

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

The following example illustrates the difference in byte order between big endian and little endian machines.

下面这个例子解释了bigendian和littleendian机器上字节顺序之间的区别。

The IA-64 Linux kernel uses little-endian by default, but allows for the possibility of using big-endian byte order.

IA-64Linux内核默认使用little-endian，但是也可以使用big-endian的字节顺序。

Big-endian format: the high byte of word data stored in the lower address, while the low byte of word data is stored in high address.

大端格式：字数据的高字节存储在低地址中，而字数据的低字节则存放在高地址中。

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?

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

Since SPARC is big-endian and x86 is little-endian, you need to consider endianness issues.

由于SPARC采用的是big-endian，而x86采用的是little-endian，因此您需要考虑endianness的问题。

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

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

So, on a big-endian system, it thought every file was empty.

因此，在高位优先系统上，它认为每个文件都是空的。

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

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

If we view 0x12345678 as two half words, 0x1234 and 0x5678, we would see the following in a big endian machine

如果将0x12345678当作两个半字来看待，分别是0x1234和0x5678，那么就会看到在bigendian机器上是下面的情况