[llvm-bugs] Issue 6213 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: SizeInBits != 0 && "invalid zero-sized type"

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #3 on issue 6213 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: SizeInBits != 0 && "invalid  
zero-sized type"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6213#c3

ClusterFuzz has detected this issue as fixed in range  
201805160754:201805170725.

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

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

Crash Type: ASSERT
Crash Address:
Crash State:
   SizeInBits != 0 && "invalid zero-sized type"
   llvm::getLLTForType
   llvm::IRTranslator::getOrCreateVReg

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201712190608:201712210617
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201805160754:201805170725

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

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.

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/20180518/65aed185/attachment.html>