-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add tests to verify assembler output -- Fix DoNotOptimize. #530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
ca7f89c
Add tests to verify assembler output -- Fix DoNotOptimize.
EricWF ffd44c9
Disable assembly tests on Bazel for now
EricWF 4d749f6
Link FIXME to github issue
EricWF 0f2f95f
Fix Tests on OS X
EricWF 4c6c517
fix strip_asm.py to work on both Linux and OS X like targets
EricWF File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,6 +6,7 @@ | |
| *.dylib | ||
| *.cmake | ||
| !/cmake/*.cmake | ||
| !/test/AssemblyTests.cmake | ||
| *~ | ||
| *.pyc | ||
| __pycache__ | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,147 @@ | ||
| # Assembly Tests | ||
|
|
||
| The Benchmark library provides a number of functions whose primary | ||
| purpose in to affect assembly generation, including `DoNotOptimize` | ||
| and `ClobberMemory`. In addition there are other functions, | ||
| such as `KeepRunning`, for which generating good assembly is paramount. | ||
|
|
||
| For these functions it's important to have tests that verify the | ||
| correctness and quality of the implementation. This requires testing | ||
| the code generated by the compiler. | ||
|
|
||
| This document describes how the Benchmark library tests compiler output, | ||
| as well as how to properly write new tests. | ||
|
|
||
|
|
||
| ## Anatomy of a Test | ||
|
|
||
| Writing a test has two steps: | ||
|
|
||
| * Write the code you want to generate assembly for. | ||
| * Add `// CHECK` lines to match against the verified assembly. | ||
|
|
||
| Example: | ||
| ```c++ | ||
|
|
||
| // CHECK-LABEL: test_add: | ||
| extern "C" int test_add() { | ||
| extern int ExternInt; | ||
| return ExternInt + 1; | ||
|
|
||
| // CHECK: movl ExternInt(%rip), %eax | ||
| // CHECK: addl %eax | ||
| // CHECK: ret | ||
| } | ||
|
|
||
| ``` | ||
|
|
||
| #### LLVM Filecheck | ||
|
|
||
| [LLVM's Filecheck](https://llvm.org/docs/CommandGuide/FileCheck.html) | ||
| is used to test the generated assembly against the `// CHECK` lines | ||
| specified in the tests source file. Please see the documentation | ||
| linked above for information on how to write `CHECK` directives. | ||
|
|
||
| #### Tips and Tricks: | ||
|
|
||
| * Tests should match the minimal amount of output required to establish | ||
| correctness. `CHECK` directives don't have to match on the exact next line | ||
| after the previous match, so tests should omit checks for unimportant | ||
| bits of assembly. ([`CHECK-NEXT`](https://llvm.org/docs/CommandGuide/FileCheck.html#the-check-next-directive) | ||
| can be used to ensure a match occurs exactly after the previous match). | ||
|
|
||
| * The tests are compiled with `-O3 -g0`. So we're only testing the | ||
| optimized output. | ||
|
|
||
| * The assembly output is further cleaned up using `tools/strip_asm.py`. | ||
| This removes comments, assembler directives, and unused labels before | ||
| the test is run. | ||
|
|
||
| * The generated and stripped assembly file for a test is output under | ||
| `<build-directory>/test/<test-name>.s` | ||
|
|
||
| * Filecheck supports using [`CHECK` prefixes](https://llvm.org/docs/CommandGuide/FileCheck.html#cmdoption-check-prefixes) | ||
| to specify lines that should only match in certain situations. | ||
| The Benchmark tests use `CHECK-CLANG` and `CHECK-GNU` for lines that | ||
| are only expected to match Clang or GCC's output respectively. Normal | ||
| `CHECK` lines match against all compilers. (Note: `CHECK-NOT` and | ||
| `CHECK-LABEL` are NOT prefixes. They are versions of non-prefixed | ||
| `CHECK` lines) | ||
|
|
||
| * Use `extern "C"` to disable name mangling for specific functions. This | ||
| makes them easier to name in the `CHECK` lines. | ||
|
|
||
|
|
||
| ## Problems Writing Portable Tests | ||
|
|
||
| Writing tests which check the code generated by a compiler are | ||
| inherently non-portable. Different compilers and even different compiler | ||
| versions may generate entirely different code. The Benchmark tests | ||
| must tolerate this. | ||
|
|
||
| LLVM Filecheck provides a number of mechanisms to help write | ||
| "more portable" tests; including [matching using regular expressions](https://llvm.org/docs/CommandGuide/FileCheck.html#filecheck-pattern-matching-syntax), | ||
| allowing the creation of [named variables](https://llvm.org/docs/CommandGuide/FileCheck.html#filecheck-variables) | ||
| for later matching, and [checking non-sequential matches](https://llvm.org/docs/CommandGuide/FileCheck.html#the-check-dag-directive). | ||
|
|
||
| #### Capturing Variables | ||
|
|
||
| For example, say GCC stores a variable in a register but Clang stores | ||
| it in memory. To write a test that tolerates both cases we "capture" | ||
| the destination of the store, and then use the captured expression | ||
| to write the remainder of the test. | ||
|
|
||
| ```c++ | ||
| // CHECK-LABEL: test_div_no_op_into_shr: | ||
| extern "C" void test_div_no_op_into_shr(int value) { | ||
| int divisor = 2; | ||
| benchmark::DoNotOptimize(divisor); // hide the value from the optimizer | ||
| return value / divisor; | ||
|
|
||
| // CHECK: movl $2, [[DEST:.*]] | ||
| // CHECK: idivl [[DEST]] | ||
| // CHECK: ret | ||
| } | ||
| ``` | ||
|
|
||
| #### Using Regular Expressions to Match Differing Output | ||
|
|
||
| Often tests require testing assembly lines which may subtly differ | ||
| between compilers or compiler versions. A common example of this | ||
| is matching stack frame addresses. In this case regular expressions | ||
| can be used to match the differing bits of output. For example: | ||
|
|
||
| ```c++ | ||
| int ExternInt; | ||
| struct Point { int x, y, z; }; | ||
|
|
||
| // CHECK-LABEL: test_store_point: | ||
| extern "C" void test_store_point() { | ||
| Point p{ExternInt, ExternInt, ExternInt}; | ||
| benchmark::DoNotOptimize(p); | ||
|
|
||
| // CHECK: movl ExternInt(%rip), %eax | ||
| // CHECK: movl %eax, -{{[0-9]+}}(%rsp) | ||
| // CHECK: movl %eax, -{{[0-9]+}}(%rsp) | ||
| // CHECK: movl %eax, -{{[0-9]+}}(%rsp) | ||
| // CHECK: ret | ||
| } | ||
| ``` | ||
|
|
||
| ## Current Requirements and Limitations | ||
|
|
||
| The tests require Filecheck to be installed along the `PATH` of the | ||
| build machine. Otherwise the tests will be disabled. | ||
|
|
||
| Additionally, as mentioned in the previous section, codegen tests are | ||
| inherently non-portable. Currently the tests are limited to: | ||
|
|
||
| * x86_64 targets. | ||
| * Compiled with GCC or Clang | ||
|
|
||
| Further work could be done, at least on a limited basis, to extend the | ||
| tests to other architectures and compilers (using `CHECK` prefixes). | ||
|
|
||
| Furthermore, the tests fail for builds which specify additional flags | ||
| that modify code generation, including `--coverage` or `-fsanitize=`. | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,45 @@ | ||
|
|
||
|
|
||
| set(ASM_TEST_FLAGS "") | ||
| check_cxx_compiler_flag(-O3 BENCHMARK_HAS_O3_FLAG) | ||
| if (BENCHMARK_HAS_O3_FLAG) | ||
| list(APPEND ASM_TEST_FLAGS -O3) | ||
| endif() | ||
|
|
||
| check_cxx_compiler_flag(-g0 BENCHMARK_HAS_G0_FLAG) | ||
| if (BENCHMARK_HAS_G0_FLAG) | ||
| list(APPEND ASM_TEST_FLAGS -g0) | ||
| endif() | ||
|
|
||
| check_cxx_compiler_flag(-fno-stack-protector BENCHMARK_HAS_FNO_STACK_PROTECTOR_FLAG) | ||
| if (BENCHMARK_HAS_FNO_STACK_PROTECTOR_FLAG) | ||
| list(APPEND ASM_TEST_FLAGS -fno-stack-protector) | ||
| endif() | ||
|
|
||
| split_list(ASM_TEST_FLAGS) | ||
| string(TOUPPER "${CMAKE_CXX_COMPILER_ID}" ASM_TEST_COMPILER) | ||
|
|
||
| macro(add_filecheck_test name) | ||
| cmake_parse_arguments(ARG "" "" "CHECK_PREFIXES" ${ARGV}) | ||
| add_library(${name} OBJECT ${name}.cc) | ||
| set_target_properties(${name} PROPERTIES COMPILE_FLAGS "-S ${ASM_TEST_FLAGS}") | ||
| set(ASM_OUTPUT_FILE "${CMAKE_CURRENT_BINARY_DIR}/${name}.s") | ||
| add_custom_target(copy_${name} ALL | ||
| COMMAND ${PROJECT_SOURCE_DIR}/tools/strip_asm.py | ||
| $<TARGET_OBJECTS:${name}> | ||
| ${ASM_OUTPUT_FILE} | ||
| BYPRODUCTS ${ASM_OUTPUT_FILE}) | ||
| add_dependencies(copy_${name} ${name}) | ||
| if (NOT ARG_CHECK_PREFIXES) | ||
| set(ARG_CHECK_PREFIXES "CHECK") | ||
| endif() | ||
| foreach(prefix ${ARG_CHECK_PREFIXES}) | ||
| add_test(NAME run_${name}_${prefix} | ||
| COMMAND | ||
| ${LLVM_FILECHECK_EXE} ${name}.cc | ||
| --input-file=${ASM_OUTPUT_FILE} | ||
| --check-prefixes=CHECK,CHECK-${ASM_TEST_COMPILER} | ||
| WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}) | ||
| endforeach() | ||
| endmacro() | ||
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should be ### i think, as you're only at ## above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it's no matter, I actually prefer having the smaller section headers for these bits. IMHO it's looks nicer and flows better.