Checker: Rename assertions to statements
Credits: this patch was originally written by David Brazdil
(dbrazdil@google.com) and remained untouched.
Author: Fabio Rinaldi
Committer: Artem Serov
Bug: 147876827
Test: art/tools/checker/run_unit_tests.py
Change-Id: Ib166fe4160508fc8c9ff0dbf0590ecd89b94c247
diff --git a/tools/checker/README b/tools/checker/README
index 8a6b128..7056856 100644
--- a/tools/checker/README
+++ b/tools/checker/README
@@ -1,13 +1,13 @@
Checker is a testing tool which compiles a given test file and compares the
state of the control-flow graph before and after each optimization pass
-against a set of assertions specified alongside the tests.
+against a set of statements specified alongside the tests.
Tests are written in Java or Smali, turned into DEX and compiled with the
-Optimizing compiler. "Check lines" are assertions formatted as comments of the
+Optimizing compiler. "Check lines" are statements formatted as comments of the
source file. They begin with prefix "/// CHECK" or "## CHECK", respectively,
followed by a pattern that the engine attempts to match in the compiler output.
-Assertions are tested in groups which correspond to the individual compiler
+Statements are tested in groups which correspond to the individual compiler
passes. Each group of check lines therefore must start with a 'CHECK-START'
header which specifies the output group it should be tested against. The group
name must exactly match one of the groups recognized in the output (they can
@@ -27,7 +27,7 @@
later than lines matched against any preceeding checks and
earlier than lines matched against any subsequent checks.
Surrounding non-negative checks (or boundaries of the group)
- therefore create a scope within which the assertion is verified.
+ therefore create a scope within which the statement is verified.
- CHECK-NEXT: Must match the output line which comes right after the line which
matched the previous check. Cannot be used after any but the
in-order CHECK.
@@ -47,7 +47,7 @@
be redefined or used undefined.
Example:
- The following assertions can be placed in a Java source file:
+ The following statements can be placed in a Java source file:
/// CHECK-START: int MyClass.MyMethod() constant_folding (after)
/// CHECK: <<ID:i\d+>> IntConstant {{11|22}}