January 23, 2013 at 18:37Support for ARM architecture appears in Google Native Client
Native Client (NaCl) allows browser-based applications to run native low-level code in an isolated sandbox. Thanks to this, the parts of performance that are critical for performance can be rewritten in C or C ++. Until now, NaCl could only work on x86-compatible computers. ARM support is of great importance to Google, since the younger laptop models on Google Chrome OS are built on the ARM architecture.
Everything you need to compile code for ARM is in the latest Native Client SDK. Google primarily seeks to ensure the work of NaCl on Samsung Chromebooks, it is too early to talk about full support for all ARM devices.
The next big goal for NaCL developers is the Portable Native Client (PNaCl), which can compile LLVM into bitcodethereby ensuring maximum compatibility with many existing and future architectures. The binding of the Native Client to a specific iron architecture is one of the main claims of third-party developers to this technology (as you know, Mozilla is pretty cool with NaCl so far). PNaCl may be able to solve this problem.
Source - Chromium Blog .
Everything you need to compile code for ARM is in the latest Native Client SDK. Google primarily seeks to ensure the work of NaCl on Samsung Chromebooks, it is too early to talk about full support for all ARM devices.
The next big goal for NaCL developers is the Portable Native Client (PNaCl), which can compile LLVM into bitcodethereby ensuring maximum compatibility with many existing and future architectures. The binding of the Native Client to a specific iron architecture is one of the main claims of third-party developers to this technology (as you know, Mozilla is pretty cool with NaCl so far). PNaCl may be able to solve this problem.
Source - Chromium Blog .