Give you an example, if you want to save 0x12345678 to 0x10000000, In little endian mode: 0x78 exists 0x10000000 0x56 exists 0x10000001 0x34 exists 0x10000002 0x12 exists 0 x10000003 In big endian mode: 0x12 exists as 0x10000000 0x34 exists as 0x10000001 0x56 exists as 0x10000002 0x78 exists as 0x10000003
This is an x86 machine, little endian, I don’t know if you understand it. Let me explain a little bit, the address of a is 0x4007cd, a single byte is printed in sequence as cd 07 40 00, two bytes are printed as 07cd 0040, and four bytes are printed as 004007cd, so the big and small ends are correct It doesn't matter from the upper level. If it is at the assembly level, it is still very obvious. For example, mov al, ah and the like have to consider the issue of big and small endianness.
Whether it is big endian mode or little endian mode, the output address is the same.
All low addresses are returned.
Both are low addresses
Big and small endianness only affects the parsing order and not the address
Give you an example, if you want to save 0x12345678 to 0x10000000,
In little endian mode:
0x78 exists 0x10000000
0x56 exists 0x10000001
0x34 exists 0x10000002
0x12 exists 0 x10000003
In big endian mode:
0x12 exists as 0x10000000
0x34 exists as 0x10000001
0x56 exists as 0x10000002
0x78 exists as 0x10000003
This is an x86 machine, little endian, I don’t know if you understand it. Let me explain a little bit, the address of
a
is0x4007cd
, a single byte is printed in sequence ascd 07 40 00
, two bytes are printed as07cd 0040
, and four bytes are printed as004007cd
, so the big and small ends are correct It doesn't matter from the upper level. If it is at the assembly level, it is still very obvious. For example,mov al, ah
and the like have to consider the issue of big and small endianness.