[llvm-bugs] Issue 33605 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-gisel: ASSERT: (&MBB != &MBB.getParent()->front() || IgnoreMissingDefs) && "no reload in start

[ClusterFuzz-External via monorail via llvm-bugs]

Status: New
Owner: ----
CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, 
d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, 
llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, 
mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com 
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible 
Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-04-23
Type: Bug

New issue 33605 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--aarch64-gisel: 
ASSERT: (&MBB != &MBB.getParent()->front() || IgnoreMissingDefs) && "no reload 
in start 
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33605

Detailed Report: https://oss-fuzz.com/testcase?key=6349367247241216

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: llvm-isel-fuzzer--aarch64-gisel
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  (&MBB != &MBB.getParent()->front() || IgnoreMissingDefs) && "no reload in 
start 
  RegAllocFast::allocateBasicBlock
  RegAllocFast::runOnMachineFunction
  
Sanitizer: address (ASAN)

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

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

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for 
instructions to reproduce this bug locally.
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. 
Comments on individual Monorail issues are not monitored.

-- 
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.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs