[llvm-bugs] Issue 3725 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: getMinSignedBits() <= 64 && "Too many bits for int64_t"

[monor… via monorail via llvm-bugs]

Comment #2 on issue 3725 by  
monor... at clusterfuzz-external.iam.gserviceaccount.com:  
llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: getMinSignedBits() <= 64 && "Too  
many bits for int64_t"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3725#c2

ClusterFuzz has detected this issue as fixed in range  
201710300453:201710310454.

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

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:
   getMinSignedBits() <= 64 && "Too many bits for int64_t"
   AddressingModeMatcher::matchOperationAddr
   AddressingModeMatcher::matchAddr

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710300453:201710310454

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

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/20171031/2a069ac7/attachment.html>