Re: Architectures where unaligned access is (not) OK?
On 21/11/14 13:21, Thorsten Glaser wrote:
> On Fri, 21 Nov 2014, Simon McVittie wrote:
>> failing to start up on armel due to unaligned memory accesses. lzo2 has
>> a cpp macro, LZO_CFG_NO_UNALIGNED which can be defined to stop it doing
>> "clever" things with casting pointers.
>
> Please define this macro unconditionally:
[followed by a bunch of reasons that look sensible]
Thanks. Based on this and the similar feedback from Bernhard and Wookey,
I'm going to propose an NMU that does that.
Thanks,
S
Reply to: