Home
last modified time | relevance | path

Searched refs:how (Results 1 – 16 of 16) sorted by relevance

/bionic/libc/bionic/
Dsigprocmask.cpp44 int sigprocmask(int how, in sigprocmask() argument
56 if (sigprocmask64(how, new_set_ptr, &old_set.sigset64) == -1) { in sigprocmask()
67 int sigprocmask64(int how, in sigprocmask64() argument
71 if (new_set && how != SIG_BLOCK && how != SIG_UNBLOCK && how != SIG_SETMASK) { in sigprocmask64()
79 mutable_new_set = filter_reserved_signals(*new_set, how); in sigprocmask64()
82 return __rt_sigprocmask(how, mutable_new_set_ptr, old_set, sizeof(*new_set)); in sigprocmask64()
Dsignal.cpp49 int pthread_sigmask(int how, const sigset_t* new_set, sigset_t* old_set) { in pthread_sigmask() argument
51 return (sigprocmask(how, new_set, old_set) == -1) ? errno : 0; in pthread_sigmask()
54 int pthread_sigmask64(int how, const sigset64_t* new_set, sigset64_t* old_set) { in pthread_sigmask64() argument
56 return (sigprocmask64(how, new_set, old_set) == -1) ? errno : 0; in pthread_sigmask64()
/bionic/libc/platform/bionic/
Dreserved_signals.h57 static inline __always_inline sigset64_t filter_reserved_signals(sigset64_t sigset, int how) { in filter_reserved_signals() argument
60 switch (how) { in filter_reserved_signals()
/bionic/docs/
Dlibc_assembler.md3 This document describes how to verify incoming assembler libc routines.
8 have any bugs. See the [Testing](#Testing) section for details about how to
14 the [Unwind Info](#unwind-info) section for details about how to verify this.
39 and pushed on to the device. The commands below show how to do this.
56 Here is an example of how the benchmark should be executed. For this
67 how to add a benchmark for a function that doesn't already exist.
144 **bionic/tests/string\_test.cpp** for examples of how to use it.
157 information indicating how to get the register.
Dclang_fortify_anatomy.md11 The intent of this document is to run through the minutiae of how Clang FORTIFY
15 getting up-to-speed on how things function can be quite difficult.
93 All talk of GCC-focused implementations and how to merge Clang and GCC
100 FORTIFY functions in Bionic, breaking down how each part of these functions
101 work, and how the pieces fit together to provide FORTIFY-like functionality.
194 So let's walk through this step by step, to see how FORTIFY does what it says on
201 `if (...) { ... }` can be optimized out. Depending on how late this happens,
395 In the above breakdown, it was shown how Clang and Bionic work together to:
454 `open("foo", 0, "how do you convert a const char[N] to mode_t?");`. The only
549 One yet-unaddressed aspect of the above is how `&open` works. This is thankfully
[all …]
DEINTR.md31 can't ignore them instead, because some of them are critical to how ART works.
48 to interrupt another thread (in fact, that's how interruption of threads
Dfdsan.md47 …file descriptor mismanagement by enforcing file descriptor ownership. Like how most memory allocat…
70 *No, really, how do I use fdsan?*
Dnative_allocator.md2 This document describes how to verify the native memory allocator on Android.
196 These are the benchmarks that examine how the allocator handles multiple
Dstatus.md312 and in an attempt to flush out racy code, we changed how an invalid
Delf-tls.md633 * It's unclear how many Android apps use Go. There are at least two with 1,000,000+ installs.
680 * When linking an executable, the static linker needs to know how TLS is allocated because it
/bionic/libc/kernel/uapi/linux/
Dauto_dev-ioctl.h54 __u32 how; member
/bionic/libc/malloc_debug/
DREADME_marshmallow_and_earlier.md7 This documentation describes how to enable this feature on API level
Dmalloc_debug.cpp235 static inline int __rt_sigprocmask(int how, const sigset64_t* new_set, sigset64_t* old_set, in __rt_sigprocmask() argument
237 return syscall(SYS_rt_sigprocmask, how, new_set, old_set, sigset_size); in __rt_sigprocmask()
DREADME.md7 This documentation describes how to enable this feature on Android N or later
309 This option only has meaning if free\_track is set. It indicates how many
374 Below is how each type of allocation/free call ends up in the file dump.
/bionic/benchmarks/
DREADME.md106 Google Benchmark uses two settings to control how many times to run each benchmark, "iterations" and
/bionic/
DREADME.md34 The C++ ABI support functions. The C++ compiler doesn't know how to implement
163 See also the notes below for how to deal with tricky cases like `off_t`.