Author Topic: Does ARM® NEON™ make sense for jPCT-AE?  (Read 661 times)

Offline kiffa

  • long
  • ***
  • Posts: 199
    • View Profile
Does ARM® NEON™ make sense for jPCT-AE?
« on: October 24, 2013, 05:29:27 am »
NEON is ARM's Single Input Multiple Data (SIMD) architecture available on most Android ARM powered devices. It is a powerful engine for accelerating processing of media, augmented reality, gaming graphics and physics engines, DSP, etc.

And there is an  open source project of NEON targeting Android and Linux apps. Project Ne10 has been set up to provide a set of common, useful functions which have been heavily optimized for the ARM Architecture and provide consistent well tested behavior that can be easily incorporated into applications.

Maybe jPCT-AE can benefit form this.

ARM's introduce:
http://www.arm.com/community/software-enablement/google/solution-center-android/advanced-app-dev.php

Project Ne10:
http://projectne10.github.io/Ne10/


Offline EgonOlsen

  • Administrator
  • quad
  • *****
  • Posts: 11745
    • View Profile
    • http://www.jpct.net
Re: Does ARM® NEON™ make sense for jPCT-AE?
« Reply #1 on: October 24, 2013, 08:50:05 am »
Not really usable in this state IMHO. You would have to include it as native calls and number crunching usually isn't that much of a problem so that the additional overhead would eat up the potential benefits. They would have to include support for this into the VM itself.