ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Valentin Kulichenko <valentin.kuliche...@gmail.com>
Subject Re: Ignite ARM Unsafe GetFloat Segmentation Fault
Date Wed, 16 Sep 2015 06:22:14 GMT
I think that at least our direct marshalling is incompatible with big
endian, because DirectByteBufferStream always uses Unsafe. We should have
something similar to PortablePrimitives (or even this specific class) there
and automatically switch to byte-by-byte processing if needed.

-Val

On Tue, Sep 15, 2015 at 11:15 PM, Denis Magda <dmagda@gridgain.com> wrote:

> ARM device may be working in big endian mode. This can definitely cause
> issues with Unsafe that uses predefined x86/x64 offsets (for little endian)
> in Ignite code.
>
> I'll dig deeply to prove my conjecture and can respond the user later.
>
> --
> Denis
>
>
> On 9/16/2015 4:48 AM, Dmitriy Setrakyan wrote:
>
>> Igniters,
>>
>> There was a question on SO about using Ignite with ARM:
>>
>> http://stackoverflow.com/questions/32592881/apache-ignite-arm-unsafe-getfloat-segmentation-fault
>>
>> Does anyone have any experience with ARM to shed some light on the issue
>> user is having?
>>
>> Thanks,
>> D.
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message