Lines Matching refs:that

9 verify that the routine is being properly tested.
10 * Rerun the benchmarks using the updated image that uses the code for
13 * Verify that unwind information for new routine looks correct. See
17 Make sure that you benchmark both the big and little cores to verify that
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.
94 that if the device does not get up to the maximum cpu frequency, the results
99 Another potential issue is that the device can overheat when running the
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
113 guarantee that you only run the single benchmark, you can execute the benchmark
118 NOTE: It is assumed that these commands are executed in adb as the shell user
124 Run the bionic tests to verify that the new routines are valid. However,
125 you should verify that there is coverage of the new routines. This is
130 When verifying an assembler routine that operates on buffer data (such as
142 functions that can be used to verify the above corner cases. See the
147 It is also important to verify that the unwind information for these
150 * Verify that all labels are of the format .LXXX, where XXX is any valid string
152 will be generated that include these labels. In that case, you will get
154 * Verify that all places where pop/pushes or instructions that modify the
156 verify that when registers are pushed on the stack that there is cfi
158 * Verify that only cfi directives are being used. This only matters for