Home
last modified time | relevance | path

Searched refs:be (Results 1 – 25 of 58) sorted by relevance

123

/bionic/libc/upstream-openbsd/lib/libc/gdtoa/
Dldtoa.c61 int be, kind; in __ldtoa() local
75 be = p->ext_exp - (LDBL_MAX_EXP - 1) - (LDBL_MANT_DIG - 1); in __ldtoa()
90 be++; in __ldtoa()
102 ret = gdtoa(&fpi, be, vbits, &kind, mode, ndigits, decpt, rve); in __ldtoa()
Dgdtoa.c43 ULong *be, *x, *x0; local
58 be = bits + ((nbits - 1) >> kshift);
65 } while(++bits <= be);
116 (fpi, be, bits, kindp, mode, ndigits, decpt, rve) in gdtoa() argument
117 FPI *fpi; int be; ULong *bits; in gdtoa()
120 (FPI *fpi, int be, ULong *bits, int *kindp, int mode, int ndigits, int *decpt, char **rve)
193 be0 = be;
196 be += i;
207 i = be + bbits - 1;
253 j = be + bbits - 1;
[all …]
Ddtoa.c118 int bbits, b2, b5, be, dig, i, ieps, ilim, ilim0, ilim1, local
200 b = d2b(dval(&d), &be, &bbits);
249 i = bbits + be + (Bias + (P-1) - 1);
442 if (be >= 0 && k <= Int_max) {
504 denorm ? be + (Bias + (P-1) - 1 + 1) :
507 1 + 4*P - 3 - bbits + ((bbits + be - 1) & 3);
/bionic/docs/
Dfdtrack.md14 callbacks upon file descriptor creation and destruction. This function can be
15 called at any point in order to start capturing events, but be sure to properly
16 handle unbalanced closes. This callback may be called from an async signal safe
31 `fdtrack_iterate` can be used (warning: this interface is currently unstable,
32 don't use it in code that can be used on multiple platform versions.)
37 backtraces for a while and then triggering a dump can be sufficient.
41 This dumps the output to logcat, which will be available in both the tombstone
55 * Slow - infeasible to be used always in latency-sensitive processes
62 * Requires -fno-omit-frame-pointer to be used on all code being unwound
Dnative_allocator.md3 This procedure should be followed when upgrading or moving to a new allocator.
8 [Performance Trace Benchmarks](#performance-trace-benchmarks) should be run.
13 systems and be a bit slower, but take less RSS. To enable the svelte config,
45 system. It is meant to be called after a call to `malloc_disable` to
62 implementation, but it should be a reasonable amount of time. The jemalloc
80 idea is that this can be called to purge memory that has not been
86 These are the tests that should be run to verify an allocator is
100 The allocation tests are not meant to be complete, so it is expected
101 that a native allocator will have its own set of tests that can be run.
136 address space is consumed. For 64 bit executables, this can be ignored.
[all …]
Dclang_fortify_anatomy.md2 *determined that it'd be good to hold in Bionic's docs, too. Due to the*
15 getting up-to-speed on how things function can be quite difficult.
38 because FORTIFY has significant flexibility in what it considers to be an
60 Textually, quite a bit can be shared between a FORTIFY implementation for GCC
105 make similar promises with respect to FORTIFY compiling to be zero-overhead in
110 **In general, when reading the below, be prepared for exceptions, subtlety, and
116 Because FORTIFY should be mostly transparent to developers, there are inherent
119 `memcpy` call with `_FORTIFY_SOURCE` enabled needs to be able to refer to the
142 - Compiling away to be zero overhead when none of the buffer sizes can be
151 is Android-specific (and orthogonal to FORTIFY anyway), so it will be ignored.
[all …]
Ddefines.md4 when can be quite tricky. This document describes the most common choices
26 If your code can be built targeting a variety of different OS versions, use
31 One thing to note (if your code may also be built as part of the OS itself) is
46 If your code can be built either as part of an app _or_ as part of the OS
53 If your code can be built with a variety of different NDK versions, and needs to
55 the NDK you're being built with. Usually only `__NDK_MAJOR__` will be necessary.
Dfdsan.md12 …be much more difficult to diagnose and fix. With `malloc` and `free`, implementations have free re…
47 …andled by types such as `std::unique_ptr`, almost all file descriptors can be associated with a un…
49 …be something that uniquely identifies the object (object address for native objects and `System.id…
65 In Android Q, fdsan has a global default of warn-once. fdsan can be made more or less strict at run…
123 When running the program, the threads' executions will be interleaved as follows:
162 Now that we've guarded the file descriptor with fdsan, we should be able to find where the double c…
167 Abort message: 'attempted to close file descriptor 3, expected to be unowned, actually owned by uni…
190 The reason for this is (hopefully!) not a bug in fdsan, and will commonly be seen when tracking dow…
208 Abort message: 'attempted to close file descriptor 3, expected to be unowned, actually owned by uni…
231 In a real application, things are probably not going to be as detectable or reproducible as our toy…
[all …]
Dlibc_assembler.md34 routines. For most routines, there should already be benchmarks available.
38 The bionic benchmarks are not built by default, they must be built separately
56 Here is an example of how the benchmark should be executed. For this
82 …***WARNING*** CPU scaling is enabled, the benchmark real time measurements may be noisy and will i…
142 functions that can be used to verify the above corner cases. See the
152 will be generated that include these labels. In that case, you will get
161 This list is not meant to be exhaustive, but a minimal set of items to verify
164 can be drastically different for the target of the branch and for the
D32-bit-abi.md8 Android does not require the `_LARGEFILE_SOURCE` macro to be used to make
12 Android also does not require the `_LARGEFILE64_SOURCE` macro to be used
15 level will be visible.
48 flag that should never be set by user code but sometimes is (by zlib,
97 an equivalent to `_FILE_OFFSET_BITS=64`, which we wouldn't be able
121 these functions. Since LP32 is unlikely to be still supported long before
Delf-tls.md24 architecture-specific thread pointer (TP) and can be accessed very efficiently -- typically just a
25 few instructions. TLS variables belonging to dlopen'ed shared objects, on the other hand, may be
45 if it hasn't been allocated yet). If the executable has a TLS segment, then it will always be module
46 1, and its storage will always be immediately after (or before) the TP. In variant 1, the TP is
66 A TLS variable may be in a different module than the reference.
153 (XXX: LD might be important for C++ `thread_local` variables -- even a single `thread_local`
159 object), then its offset from the TP is known at load-time. The variable can be accessed with a few
165 // tls_var could be defined in the executable, or it could be defined
187 part of the executable (and referenced from the executable), then a GOT access can be avoided. The
201 * Code compiled with `-fpic` could be in a shared object, so use GD/LD.
[all …]
/bionic/benchmarks/
DREADME.md24 See the `benchmarks/run-on-host.sh` script. The host benchmarks can be run with 32-bit or 64-bit
29 Suites are stored in the `suites/` directory and can be chosen with the command line flag
34 the file will be found as relative to the current directory. If the option specifies the full path
35 to an XML file such as `/data/nativetest/suites/example.xml`, it will be used as-is.
66 For the sake of brevity, multiple runs can be scheduled in one XML element by putting one of the
75 Definitions for these can be found in bionic_benchmarks.cpp, and example usages can be found in
80 `bionic-benchmarks` also has its own set of unit tests, which can be run from the binary in
126 There are 4 runs, each with 25290525 iterations. Measurements for the individual runs can be
140 To get consistent results between runs, it can sometimes be helpful to restrict a benchmark to
144 A core can be selected for `bionic-benchmarks` using the `--bionic_cpu` option or using the
[all …]
/bionic/libc/malloc_debug/
DREADME.md41 Malloc debug is controlled by individual options. Each option can be enabled
42 individually, or in a group of other options. Every single option can be
52 modified. If any part of the front guard is modified, an error will be reported
59 The default is 32 bytes, the max bytes is 16384. SIZE\_BYTES will be
78 modified. If any part of the rear guard is modified, an error will be reported
110 this can be set to is 256.
137 this can be set to is 256.
145 dump heap data to be dumped to a file when the program exits. If the backtrace
149 The file location can be changed by setting the backtrace\_dump\_prefix
160 on the signal will be backtrace\_dump\_prefix.**PID**.txt. The filename chosen
[all …]
DREADME_marshmallow_and_earlier.md15 On these old versions of the OS, you must be able to set system properties
50 first 16 frames of the backtrace will be captured.
55 All of the currently live allocations will be tracked and can be retrieved
91 only up to 16 frames will be recorded.
112 cause malloc debug to only be used on processes with that name. For example,
DREADME_api.md3 Malloc debug can be used to get information on all of the live allocations
4 in a process. The libc library in Android exports two calls that can be
5 used to gather this data from a process. This tracking can be enabled using
/bionic/libc/
DSECCOMP_BLOCKLIST_COMMON.TXT5 # Any entry in the blocklist must be in the syscalls file and not be in the allowlist file
DSECCOMP_BLOCKLIST_APP.TXT5 # Any entry in the blocklist must be in the syscalls file and not be in the allowlist file
10 # including capset and setresuid. This is because the seccomp filter must be installed while
/bionic/linker/
Dld.config.format.md3 This document describes format of /system/etc/ld.config.txt file. This file can be used to customize
18 The mappings should be defined between start of ld.config.txt and the first section.
41 # This property can be used to declare additional namespaces. Note that there is always the default
83 # [Deprecated] This defines what libraries are allowed to be loaded from ns1
85 # This defines what libraries are allowed to be loaded from ns1
/bionic/
Dandroid-changes-for-ndk-developers.md22 will be tied to an app's target API level:
55 Alternatively, if you don't have too many dependencies, it can be easiest to
90 The dlopen(3) RTLD_LOCAL flag used to be ignored but is implemented
93 be affected (unless they explicitly used RTLD_GLOBAL). With RTLD_LOCAL,
94 symbols will not be made available to libraries loaded by later calls
146 that you want to load directly from your APK must be page aligned
152 "my_zip_file.zip!/libs/libstuff.so". As with APKs, the library must be
176 On devices running API level 26 to API level 30, this compatibility mode could be
199 (libcutils.so) can be copied to the project. As a long term solution
200 the relevant code must be copied to the project tree. SSL/Media/JNI
[all …]
DREADME.md66 # because it's architecture-specific. There will be a .mk file in here that
100 # The generate_uapi_headers.sh script should be used to go from a kernel
102 # architecture-specific details. The update_all.py script should then be
104 # The files in bionic must not be edited directly because any local changes
105 # will be overwritten by the next update. "Updating kernel header files"
126 # but in order to actually be able to compile this code in our tree
140 # legacy mess that needs to be sorted out, either by replacing it with
175 The answer may be "yes" if the system call has three/four distinct
190 should really be adding this or not!)
198 for the first release your system call wrapper will be in. See
[all …]
/bionic/tests/
Dlibgen_basename_test.cpp27 #error basename should not be defined at this point
39 #error basename should be defined at this point
Dsys_syscall_test.cpp28 #error SYS_mmap2 should not be defined for LP64
/bionic/libc/kernel/android/
DREADME.md10 declarations that can't be directly used by userspace. The glibc
16 Any modification should first be made there then copied into the scsi
/bionic/libc/kernel/
DREADME.md4 can safely be included by userland applications and libraries.
15 They can be included from C++, or when compiling code in strict ANSI mode.
16 They can be also included before or after any Bionic C library header.
33 be used as uapi headers. The tools to process the kernel headers will
35 to be hand-modified.
85 It is expected that a kernel update should only be performed on a valid tag.
/bionic/libc/arch-x86_64/bionic/
Dsyscall.S45 # (Not all will be valid, depending on the syscall.)

123