Searched refs:as (Results 1 – 25 of 31) sorted by relevance
12
10 is typically a good choice when you use libc API that's only in bionic, such as18 useful as you might think, and one of the other choices on this page is usually31 One thing to note (if your code may also be built as part of the OS itself) is33 obvious "next" API level such as 19. Once the API level has been decided, the39 choice when you use Linux-specific API, such as a Linux-specific system call or46 If your code can be built either as part of an app _or_ as part of the OS48 This is typically a good choice when your code uses non-NDK API if it's built as
11 and distribution as defined by Sections 1 through 9 of this document.37 Object form, made available under the License, as indicated by a44 represent, as a whole, an original work of authorship. For the purposes61 designated in writing by the copyright owner as "Not a Contribution."77 (except as stated in this section) patent license to make, have made,88 as of the date such litigation is filed.107 (d) If the Work includes a "NOTICE" text file as part of its113 as part of the Derivative Works; within the Source form or120 or as an addendum to the NOTICE text from the Work, provided122 as modifying the License.[all …]
92 of allocation routines such as what happens when a non-power of two alignment204 results, but, as mentioned before, these microbenchmark numbers should205 not be used as absolutes for determining if an allocator is worth using.253 in a real world allocation scenario. SQL operations were chosen as a267 These numbers should be as performant as the current allocator.279 nearly as performant as the current allocator.319 on a thread as if it was rerunning the real trace. The only issue is that344 checked in as zip files.358 they should not be used as absolute value for comparison against the359 current allocator. But, they should be in the same range as the current[all …]
12 …as *use-after-close* and *double-close*. These errors are direct analogues of the memory allocatio…47 …how most memory allocations can have their ownership handled by types such as `std::unique_ptr`, a…53 ### Enabling fdsan (as a user)61 - Same as warn-once, except without disabling after the first warning.123 When running the program, the threads' executions will be interleaved as follows:190 …d for closing `victim`'s fd. If we store `bystander`'s fd in a `unique_fd` as well, we should get …231 In a real application, things are probably not going to be as detectable or reproducible as our toy…233 ### Enabling fdsan (as a C++ library implementer)
13 system call, for which there is no equivalent "partial" success, such as58 system call as long as the result is -1 and errno is `EINTR`.
111 * Full C11 `<threads.h>` (available as inlines for older API levels).133 * Using `%n` with the printf family is now reported as a FORTIFY failure.164 runtime and reported as a FORTIFY failure.166 reported as a FORTIFY failure.193 reported as a FORTIFY failure. Most commonly this is a result of confusing349 Note that this doesn't change behavior as much as you might think: the376 inherently non-portable as-is.) The best alternative on Android is to397 overrun is detected, the program is safely aborted as in this
13 to make `off64_t` and corresponding functions such as `ftruncate64` available.24 and replaces each `off_t` function with its `off64_t` counterpart, such as91 The header `<time64.h>` and type `time64_t` exist as a workaround,109 mutexes for tids that don't fit in 16 bits. This typically manifests as
118 NOTE: It is assumed that these commands are executed in adb as the shell user120 machine, you might need to escape the special shell characters such as **$**.130 When verifying an assembler routine that operates on buffer data (such as163 to verify unwind cases, such as around branches, where unwind information
57 divergence is an artifact of Clang and GCC's differing architecture as130 `memcpy` as though `_FORTIFY_SOURCE` were disabled.218 signature as `__builtin_mempcpy`. `pass_object_size` is a Clang attribute that262 - Evaluate it as a constant.366 in our IR. This can have negative effects, such as distorting inlining costs and476 This exists as a way for us to call `__builtin_open` without needing clang to683 `__builtin_object_size(p, 0)` is more or less as simple as the example in the745 passes the value of that into the callee as an invisible parameter. All calls to787 FORTIFY exists mostly for visual consistency, simplicity, and as a useful way to798 // and is able to work with that as though the function were defined inline.[all …]
9 costly to connect a socket for each thread as some processes, such as system_server, have over 100
46 The `tests/` directory contains unit tests. Roughly arranged as one file per94 # and constants that make up the "userspace API" (uapi) available as177 library that would make more sense as the place to add the wrapper.204 underscores (so developers are free to use any of the unadorned names as206 use the same name as an existing system call (to reduce the amount of254 argument such as `off64_t` (a *pointer* to a 64-bit argument is fine, since259 implemented as two different system calls. It's usually easiest to find a324 If you make a change that is likely to have a wide effect on the tree (such as a329 either, as `make tests` covers a few additional modules, but generally speaking358 Most of the unit tests are executed by CTS. By default, CTS runs as[all …]
25 a warning, as appropriate.34 as toasts. Experience has shown that many developers don’t habitually95 to dlopen(3) (as opposed to being referenced by DT_NEEDED entries).140 your APK. Just use `System.loadLibrary("foo")` exactly as normal but set145 and reported to the user as space taken up by your app). Any .so file286 DT_NEEDED entry should be the same as the needed library's SONAME,317 libraries as the location may change from device to device.326 runtime issues such as the wrong library being loaded: the filename is433 code for which has been unloaded (as in [issue 360], fixed in API level 28).
17 run as root on the device.78 A 32 byte buffer is placed before the returned allocation (known as81 as a rear guard). This buffer is filled with the pattern (0xbb).100 are printed to the log as leaks. This isn't very useful since it tends
38 *backtrace\_size* as returned by the original call to42 backtrace and size as this allocation. On Android Nougat, this value was
118 Android devices). The format of this dumped data is the same format as173 as [libmemunreachable](https://android.googlesource.com/platform/system/memory/libmemunreachable/+/…174 to only get backtraces for sizes of allocations listed as being leaked.186 as [libmemunreachable](https://android.googlesource.com/platform/system/memory/libmemunreachable/+/…187 to only get backtraces for sizes of allocations listed as being leaked.195 as [libmemunreachable](https://android.googlesource.com/platform/system/memory/libmemunreachable/+/…196 to only get backtraces for sizes of allocations listed as being leaked.548 generated by am dumpheap -n or, as of P, by the signal or on exit.611 NUM\_ALLOCATIONS value should be treated as always 1 no matter what is715 It is possible to use the backtrace\_enable\_on\_signal option as well,
40 // library in the "data" property, but that doesn't work, because each library is listed as having a41 // "link:shared" variant (as opposed to "link:static"), whereas the cc_benchmark has no
33 be used as uapi headers. The tools to process the kernel headers will87 version, but never use that as the basis for importing new kernel headers.91 to determine which directory to use as the destination directory.
9 // embedded as the entry point, and the linker is embedded as ELF sections in340 // relocations. lld has been taught to not store them there as a bug workaround (see500 // for x86, exclude libgcc_eh.a for the same reasons as above
34 the file will be found as relative to the current directory. If the option specifies the full path35 to an XML file such as `/data/nativetest/suites/example.xml`, it will be used as-is.
84 // for x86, exclude libgcc_eh.a for the same reasons as above184 // for x86, exclude libgcc_eh.a for the same reasons as above
77 // Install these binaries in the same directory as the main benchmark binary.
755 ns_name_eq(ns_nname_ct a, size_t as, ns_nname_ct b, size_t bs) { in ns_name_eq() argument756 ns_nname_ct ae = a + as, be = b + bs; in ns_name_eq()
81 # likely to be useful as new features are added. In particular, cgroups