summaryrefslogtreecommitdiff
path: root/docs/libc_assembler.md
diff options
context:
space:
mode:
authorElliott Hughes <enh@google.com>2020-07-31 10:35:03 -0700
committerElliott Hughes <enh@google.com>2020-07-31 10:35:03 -0700
commitcf346532fccbe35666b827fbbfd2cb951dd00dc2 (patch)
treec1ab59c29e63dea1700f24edb6bfad28c9d0687f /docs/libc_assembler.md
parentb1d27cab96c7aa31470ed2a1a8b284f9422cef25 (diff)
More cleanup for #inclusivefixit.
Found manually with grep, since the script seems to miss stuff. Test: treehugger Change-Id: I5933cbade9792801d4a0bec1ccb077efa6ad8fbc
Diffstat (limited to 'docs/libc_assembler.md')
-rw-r--r--docs/libc_assembler.md3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/libc_assembler.md b/docs/libc_assembler.md
index 44c00366d..43bcfc753 100644
--- a/docs/libc_assembler.md
+++ b/docs/libc_assembler.md
@@ -10,7 +10,8 @@ verify that the routine is being properly tested.
* Rerun the benchmarks using the updated image that uses the code for
the new routine. See the [Performance](#Performance) section for details about
benchmarking.
-* Verify that unwind information for new routine looks sane. See the [Unwind Info](#unwind-info) section for details about how to verify this.
+* Verify that unwind information for new routine looks correct. See
+the [Unwind Info](#unwind-info) section for details about how to verify this.
When benchmarking, it's best to verify on the latest Pixel device supported.
Make sure that you benchmark both the big and little cores to verify that