Re: [bug-mes] mescc and Load/Store architectures

[Danny Milosavljevic]

Hi Jeremiah,

oops, the values are big numbers, so they can't be used directly in mescc-tools 
for ARM little-endian like this, we'd have to endian-swap them.

When I wrote e0811000 I expected the integer 0xe0811000 to be emitted to the 
binary output file, but it's not (for little endian).

hex2 rather takes every 2 consecutive chars as the hex code of one byte and 
emits that.

So I would like to instead write: 00 10 81 e0.

But in M1 DEFINEs it seems that I'm not allowed to enter spaces.

That's rather unfortunate.  Without having read the hex2 source code I'd 
interpret e0811000 as the number 0xe0811000, which hex2 doesn't.  Spaces would 
make it unambiguous.

pgpBwDrgL87R2.pgp
Description: OpenPGP digital signature