Support for ARM architecture added to Google Native Client
Native Client (NaCl) allows browser applications to run native low-level code in an isolated sandbox. Because of this, critical parts for performance can be rewritten to C or C ++. Until now, Nal could only work on x86-compatible computers. ARM support is of great importance to Google, as 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 that NaCl works on Samsung’s Chromebooks, and it’s too early to fully support all ARM devices.
The next big goal of the NaCL developers is the Portable Native Client (PNaCl), which can compile into the LLVM bitcode , thereby ensuring maximum compatibility with many existing and future architectures. Binding of the Native Client to a specific iron architecture is one of the main complaints of third-party developers to this technology (as you know, Mozilla is still quite cool with NaCl). Perhaps PNaCl can solve this problem.
The source is the Chromium blog .
')
Everything you need to compile code for ARM is in the latest Native Client SDK. Google primarily seeks to ensure that NaCl works on Samsung’s Chromebooks, and it’s too early to fully support all ARM devices.
The next big goal of the NaCL developers is the Portable Native Client (PNaCl), which can compile into the LLVM bitcode , thereby ensuring maximum compatibility with many existing and future architectures. Binding of the Native Client to a specific iron architecture is one of the main complaints of third-party developers to this technology (as you know, Mozilla is still quite cool with NaCl). Perhaps PNaCl can solve this problem.
The source is the Chromium blog .
')
Source: https://habr.com/ru/post/166833/
All Articles