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機器上是下面的情況