[llvm-bugs] Issue 14106 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: !AM.Disp && "Non-zero displacement is ignored with JT."

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #2 on issue 14106 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: !AM.Disp && "Non-zero  
displacement is ignored with JT."
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14106#c2

ClusterFuzz has detected this issue as fixed in range  
201904100312:201904110259.

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

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:
   !AM.Disp && "Non-zero displacement is ignored with JT."
   X86DAGToDAGISel::getAddressOperands
   X86DAGToDAGISel::selectAddr

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904100312:201904110259

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

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/20190411/6683d8ab/attachment-0001.html>