[llvm-bugs] Issue 6477 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: VPlans.size() == 1 && "Best VF has not a single VPlan."

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #8 on issue 6477 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: VPlans.size() == 1  
&& "Best VF has not a single VPlan."
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6477#c8

ClusterFuzz has detected this issue as fixed in range  
201902070427:201902080417.

Detailed report: https://oss-fuzz.com/testcase?key=5765686711287808

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_vectorize
Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_vectorize
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
   VPlans.size() == 1 && "Best VF has not a single VPlan."
   llvm::LoopVectorizationPlanner::setBestPlan
   llvm::LoopVectorizePass::processLoop

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802190622:201802200626
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902070427:201902080417

Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=5765686711287808

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on  
the test case report page.

-- 
You received this message because:
   1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190208/0843c7fc/attachment-0001.html>