[llvm-bugs] Issue 9880 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64 && "Too many bits for uint64_t"

ClusterFuzz-External via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Tue Aug 14 00:51:58 PDT 2018


Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,  
igm... 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-2018-08-14
Type: Bug

New issue 9880 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: getActiveBits() <= 64  
&& "Too many bits for uint64_t"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9880

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

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

Crash Type: ASSERT
Crash Address:
Crash State:
   getActiveBits() <= 64 && "Too many bits for uint64_t"
   llvm::InstCombiner::visitLShr
   llvm::InstCombiner::run

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801030610:201801040618

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

Issue filed automatically.

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

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/20180814/950d527b/attachment.html>


More information about the llvm-bugs mailing list