[llvm-bugs] Issue 13630 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: MRI->getVRegDef(Reg) && "Machine instr not mapped for this vreg?!"

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #2 on issue 13630 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: MRI->getVRegDef(Reg) && "Machine  
instr not mapped for this vreg?!"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13630#c2

ClusterFuzz has detected this issue as fixed in range  
201903110335:201903120333.

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

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

Crash Type: ASSERT
Crash Address:
Crash State:
   MRI->getVRegDef(Reg) && "Machine instr not mapped for this vreg?!"
   MachineLICMBase::IsLoopInvariantInst
   MachineLICMBase::runOnMachineFunction

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903050442:201903070433
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903110335:201903120333

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

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/20190312/85b46f3c/attachment.html>