[llvm-bugs] Issue 13229 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !getMember(0)->mayWriteToMemory() && "Group should have been invalidated"
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Wed Feb 20 03:06:20 PST 2019
Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,
igm... at gmail.com, mitchp at google.com, bigchees... at gmail.com,
eneyman at google.com, llvm-b... at lists.llvm.org, jfb at chromium.org,
v... at apple.com, mitchphi... at outlook.com, xpl... at gmail.com,
akils... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible
Engine-libfuzzer Proj-llvm Reported-2019-02-20
Type: Bug
New issue 13229 by ClusterFuzz-External:
llvm/llvm-opt-fuzzer--x86_64-loop_vectorize:
ASSERT: !getMember(0)->mayWriteToMemory() && "Group should have been
invalidated"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13229
Detailed report: https://oss-fuzz.com/testcase?key=5713358093811712
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:
!getMember(0)->mayWriteToMemory() && "Group should have been invalidated"
llvm::LoopVectorizationCostModel::interleavedAccessCanBeWidened
llvm::LoopVectorizationCostModel::setCostBasedWideningDecision
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201810170227:201811111623
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5713358093811712
Issue filed automatically.
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
instructions to reproduce this bug locally.
When you fix this bug, please
* mention the fix revision(s).
* state whether the bug was a short-lived regression or an old bug in any
stable releases.
* add any other useful information.
This information can help downstream consumers.
If you need to contact the OSS-Fuzz team with a question, concern, or any
other feedback, please file an issue at
https://github.com/google/oss-fuzz/issues.
--
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/20190220/b8cfaa6b/attachment.html>
More information about the llvm-bugs
mailing list