diff options
| author | Jessica Paquette <jpaquette@apple.com> | 2018-07-30 17:13:25 +0000 |
|---|---|---|
| committer | Jessica Paquette <jpaquette@apple.com> | 2018-07-30 17:13:25 +0000 |
| commit | bbcc8895bb8d476cb1006891f2e01e5fcfc9531d (patch) | |
| tree | 5731a3180e334b2c3ee44a8cbd1fd91f61fbe1b8 | |
| parent | a932cd409b861582902211690b497cafc774bee6 (diff) | |
| download | llvm-bbcc8895bb8d476cb1006891f2e01e5fcfc9531d.zip llvm-bbcc8895bb8d476cb1006891f2e01e5fcfc9531d.tar.gz llvm-bbcc8895bb8d476cb1006891f2e01e5fcfc9531d.tar.bz2 | |
Add machine verifier to arm64-opt-remarks-lazy-bfi
Previously, I thought this was a Windows failure. Then I realized it failed on
every bot that used the verifier. This makes it use the verifier always, and
adds that pass to the pipeline checks so that it's consistent across all bots.
llvm-svn: 338272
| -rw-r--r-- | llvm/test/CodeGen/AArch64/arm64-opt-remarks-lazy-bfi.ll | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/llvm/test/CodeGen/AArch64/arm64-opt-remarks-lazy-bfi.ll b/llvm/test/CodeGen/AArch64/arm64-opt-remarks-lazy-bfi.ll index 4233e56..79cf990 100644 --- a/llvm/test/CodeGen/AArch64/arm64-opt-remarks-lazy-bfi.ll +++ b/llvm/test/CodeGen/AArch64/arm64-opt-remarks-lazy-bfi.ll @@ -1,9 +1,11 @@ ; RUN: llc < %s -mtriple=arm64-apple-ios7.0 -pass-remarks-analysis=asm-printer \ +; RUN: -verify-machineinstrs \ ; RUN: -pass-remarks-with-hotness=1 -asm-verbose=0 \ ; RUN: -debug-only=lazy-machine-block-freq,block-freq \ ; RUN: -debug-pass=Executions 2>&1 | FileCheck %s -check-prefix=HOTNESS ; RUN: llc < %s -mtriple=arm64-apple-ios7.0 -pass-remarks-analysis=asm-printer \ +; RUN: -verify-machineinstrs \ ; RUN: -pass-remarks-with-hotness=0 -asm-verbose=0 \ ; RUN: -debug-only=lazy-machine-block-freq,block-freq \ ; RUN: -debug-pass=Executions 2>&1 | FileCheck %s -check-prefix=NO_HOTNESS @@ -25,13 +27,12 @@ ; Verify that we only populate MachineBFI on behalf of ORE when hotness is ; requested. (This hard-codes the previous pass to the Assembly Printer, ; please adjust accordingly.) -; Lazy Machine Block Frequency Analysis is handled using a CHECK-DAG rather than -; a CHECK-NEXT because on Windows, the 'Verify generated machine code' pass is -; also inserted. ; HOTNESS: Freeing Pass 'Machine Outliner' ; HOTNESS-NEXT: Executing Pass 'Function Pass Manager' -; HOTNESS-DAG: Executing Pass 'Lazy Machine Block Frequency Analysis' +; HOTNESS-NEXT: Executing Pass 'Verify generated machine code' +; HOTNESS-NEXT: Freeing Pass 'Verify generated machine code' +; HOTNESS-NEXT: Executing Pass 'Lazy Machine Block Frequency Analysis' ; HOTNESS-NEXT: Executing Pass 'Machine Optimization Remark Emitter' ; HOTNESS-NEXT: Building MachineBlockFrequencyInfo on the fly ; HOTNESS-NEXT: Building LoopInfo on the fly @@ -46,7 +47,9 @@ ; NO_HOTNESS: Freeing Pass 'Machine Outliner' ; NO_HOTNESS-NEXT: Executing Pass 'Function Pass Manager' -; NO_HOTNESS-DAG: Executing Pass 'Lazy Machine Block Frequency Analysis' +; NO_HOTNESS-NEXT: Executing Pass 'Verify generated machine code' +; NO_HOTNESS-NEXT: Freeing Pass 'Verify generated machine code' +; NO_HOTNESS-NEXT: Executing Pass 'Lazy Machine Block Frequency Analysis' ; NO_HOTNESS-NEXT: Executing Pass 'Machine Optimization Remark Emitter' ; NO_HOTNESS-NEXT: Executing Pass 'AArch64 Assembly Printer' |