Hi Anto,
> On 22.11.2015, at 12:10, Antonio Cuni wrote:
>
> 1) I know that ARM CPUs can be either little or big endiam. What is the case
> for our armhf machine?
Our builders are all little endian. To my knowledge most (maybe all) Linux
distributions for ARM are little endian nowadays.
>
>
Hi again,
Here's a guess. The value expected is 0x4142434445464748. The value
we read is 0xb3f4bce041424344. That hints at an off-by-4-bytes issue.
My guess is an alignment issue. When you force-cast the RPython
string to a type with an 8-bytes-per-item array, on some 32-bit
platforms it might
Hi Anto,
On Sun, Nov 22, 2015 at 12:10 PM, Antonio Cuni wrote:
> I suspect a big/little endian issue.
Fwiw, the error doesn't seem to be an endianness issue, but rather
reading garbage (and I'm pretty sure that all our ARMs are little
endian).
A bientôt,
Armin.
___
Hi David,
I am developing the "faster-rstruct" branch, which aims to speedup
struct.unpack by reading the values at once from memory, instead of
byte-by-byte as it's doing right now.
The branch works fine on x86 but fails on armhf (see e.g.
http://buildbot.pypy.org/summary/longrepr?testname=AppTe
