Search Results for "abi"

This app is used to view the third-party libraries used by applications in your device. It can view the ABI architecture of the application's native library (in general, whether the application is 64-bit or 32-bit). It can also view well-known libraries marked by The Rule Repository, and can even sort and view them according to the number of libraries references.

...Its developer experience is shaped around familiar JavaScript patterns such as Node-style file APIs, WHATWG conventions, and event-driven behavior. The SDK adds typed ergonomics over the lower-level host ABI, making capsule development easier for web and Node developers. Its main value is bringing Astrid capsule development into the JavaScript ecosystem without changing the runtime contract.

...Its purpose is to provide a minimal, size-optimized build of the native core with a clear Java/Kotlin interface to start, stop, and configure network tunnels. By exposing the core as an AAR with per-ABI artifacts, it keeps application footprints small while supporting common CPU architectures. The library abstracts process management and log streaming so host apps can control lifecycles and capture diagnostics. It’s particularly useful for developers who want to integrate secure, rule-based proxying into their own Android apps without re-implementing the native glue. ...

libjpeg-turbo is a JPEG image codec that uses SIMD instructions (MMX, SSE2, NEON, AltiVec) to accelerate baseline JPEG compression and decompression on x86, x86-64, ARM, and PowerPC systems. On such systems, libjpeg-turbo is generally 2-6x as fast as libjpeg, all else being equal. On other types of systems, libjpeg-turbo can still outperform libjpeg by a significant amount, by virtue of its highly-optimized Huffman coding routines. In many cases, the performance of libjpeg-turbo rivals...

...Some key differences compared to the former are the use of a hierarchical namespace and the use of human readable “fully qualified names” instead of GUIDs, as well as the support for basic metadata that allows the distribution of modules in binary form only, while still allowing extensive reuse. Component proxies are central to the abstraction of the ABI and allow the C++M model to do automatic marshaling of parameters, automatic lifecycle management (RAII) and to support exception handling across component (and compiler/library) boundaries. These proxies are generated with a special pre-compiler from the “module description language”.

A cross-platform framework built in C with multiple language bindings, easing the transition between languages and platforms, while maintaining ABI compatibility.

MorphMPI simulates an ABI for MPI. Applications compiled using MorphMPI can easily be relinked to use any MPI implementation on a compatible OS-cpu combination.