Lines Matching refs:to

3 This document describes how to verify incoming assembler libc routines.
7 * Update the routine, run the bionic unit tests to verify the routine doesn't
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.
16 When benchmarking, it's best to verify on the latest Pixel device supported.
17 Make sure that you benchmark both the big and little cores to verify that
28 Locking to a specific cpu:
33 The bionic benchmarks are used to verify the performance of changes to
39 and pushed on to the device. The commands below show how to do this.
57 command to work, you need to change directory to one of the above
62 The last argument is the name of the one function that you want to
66 **bionic/benchmarks/suites**. Look at the examples in that file to see
67 how to add a benchmark for a function that doesn't already exist.
69 It can take a long time to run these tests since it attempts to test a
94 that if the device does not get up to the maximum cpu frequency, the results
95 can vary wildly. It's possible to lock the cpu to the maximum frequency, but
101 or choose a device that is less likely to overheat. To detect these kind
103 always a good idea to rerun the suite a couple of times to verify that
106 If you want to verify a single benchmark result, you can run a single test
111 Where the argument to the filter argument is the name of the benchmark from
112 the output. Sometimes this filter can still match multiple benchmarks, to
119 on device. If you are trying to run this using adb directly from a host
120 machine, you might need to escape the special shell characters such as **$**.
124 Run the bionic tests to verify that the new routines are valid. However,
131 memcpy/strcpy), it's important to verify these corner cases:
135 read past the end. This kind of bug results in an infrequent and difficult to
142 functions that can be used to verify the above corner cases. See the
144 **bionic/tests/string\_test.cpp** for examples of how to use it.
147 It is also important to verify that the unwind information for these
148 routines are properly set up. Here is a quick checklist of what to check:
157 information indicating how to get the register.
159 arm32, where it's possible to use ARM specific unwind directives.
161 This list is not meant to be exhaustive, but a minimal set of items to verify
163 to verify unwind cases, such as around branches, where unwind information