ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrey Gura (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-1497) Support CPU architectures different from x86/x64
Date Wed, 03 Feb 2016 17:38:39 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrey Gura closed IGNITE-1497.
-------------------------------
    Assignee:     (was: Andrey Gura)

> Support CPU architectures different from x86/x64
> ------------------------------------------------
>
>                 Key: IGNITE-1497
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1497
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
>             Fix For: 1.6
>
>
> Ignite widely uses {{Unsafe}} instance throughout the code and the usage is mostly based
on the fact that the platform will be running on a little-endian x86/x64 machine.
> As an example the following classes work with short, int, long and other type values
bigger than 1 byte in size without taking CPU endiannes into account:
> - {{DirectByteBufferStream}};
> - {{PortableObjectOffheapImpl}};
> - {{GridUnsafeDataOutput}};
> - etc.
> This leads to VM crashes on different CPU architectures:
> - IGNITE-1493;
> - http://stackoverflow.com/questions/32592881/apache-ignite-arm-unsafe-getfloat-segmentation-fault
> All the classes that use {{Unsafe}} in Ignite have to be revisited and modified in a
way to support different CPU architectures.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message