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 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. ...

...KAFKA is a registered trademark of The Apache Software Foundation and has been licensed for use by librdkafka. librdkafka has no affiliation with and is not endorsed by The Apache Software Foundation. SASL (GSSAPI/Kerberos/SSPI, PLAIN, SCRAM, OAUTHBEARER) support. Guaranteed API stability for C & C++ APIs (ABI safety guaranteed for C). Runs on Linux, MacOS X, Windows, Solaris, FreeBSD, AIX, and more. Commercial support is available from Confluent Inc.

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...

...It is extremely memory-efficient, 10,000,000 coroutines simultaneously to run cost only 2.8 GB physical memory (run with tcmalloc, each coroutine has a 120B copy-stack size configuration). The phrase "fastest" in above means the fastest context switching implementation which complies to the Sys V ABI of Intel386 or AMD64.

...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”.