Searched refs:changes (Results 1 – 11 of 11) sorted by relevance
11 # Still the best reviewer for changes related to the dynamic linker.
12 This documentation is about making changes to bionic itself.203 ## Verifying changes255 # This will sync any *test* changes, but not *code* changes:
1 # Android changes for NDK developers3 This document details important changes related to native code14 ## How we manage incompatible changes16 Our general practice with dynamic linker behavior changes is that they110 compatibility. For example, if a library author knowingly changes147 handle platform changes. For that reason, we recommend against using
69 struct snd_firewire_tascam_change changes[0]; member
61 To make small changes in runs, you can also schedule benchmarks by passing in their name and a
55 Bionicbb polls a gmail account to find changes that need to be built. The gmail
87 changes do not introduce any errors.
1218 __u32 changes; member1235 __u32 changes; member
32 The bionic benchmarks are used to verify the performance of changes to
776 * more intrusive toolchain changes (affects both Clang and LLD)
35 call changes the backtrace for the pointer no matter whether the pointer