Searched refs:changes (Results 1 – 11 of 11) sorted by relevance
11 # Still the best reviewer for changes related to the dynamic linker.
1 # Android linker changes for NDK developers3 This document details important changes related to native code7 behavior changes.17 ## How we manage incompatible changes19 Our general practice with dynamic linker behavior changes is that they54 library and symbol lookup changes on all past (and future) Android versions.125 compatibility. For example, if a library author knowingly changes162 handle platform changes. For that reason, we recommend against using
12 This documentation is about making changes to bionic itself.198 ## Verifying changes250 # This will sync any *test* changes, but not *code* changes:
69 struct snd_firewire_tascam_change changes[0]; member
3 This document details libc/libm/libdl additions and behavior changes.6 [Android linker changes for NDK developers](../android-changes-for-ndk-developers.md)7 for changes related to native code loading in various Android releases.
33 The bionic benchmarks are used to verify the performance of changes to
776 * more intrusive toolchain changes (affects both Clang and LLD)
93 changes do not introduce any errors.
57 To make small changes in runs, you can also schedule benchmarks by passing in their name and a
1258 __u32 changes; member1275 __u32 changes; member
35 call changes the backtrace for the pointer no matter whether the pointer