[llvm-bugs] Issue 18987 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: LRegs.size() == 1 && "Can't handle this yet!"

2022-01-25 Thread ClusterFuzz-External via monorail via llvm-bugs
Updates:
Labels: ClusterFuzz-Verified
Status: Verified

Comment #2 on issue 18987 by ClusterFuzz-External: 
llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: LRegs.size() == 1 && "Can't handle 
this yet!"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18987#c2

ClusterFuzz testcase 5696628036206592 is verified as fixed in 
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=202108040600:202201250612

If this is incorrect, please file a bug on 
https://github.com/google/oss-fuzz/issues/new

-- 
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


[llvm-bugs] Issue 18987 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: LRegs.size() == 1 && "Can't handle this yet!"

2020-02-10 Thread sheriff… via monorail via llvm-bugs
Updates:
Labels: Deadline-Approaching

Comment #1 on issue 18987 by 
sheriff...@sheriffbot-1182.iam.gserviceaccount.com: 
llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: LRegs.size() == 1 && "Can't handle 
this yet!"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18987#c1

This bug is approaching its deadline for being fixed, and will be automatically 
derestricted within 7 days. If a fix is planned within 2 weeks after the 
deadline has passed, a grace extension can be granted.

- Your friendly Sheriffbot

-- 
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


[llvm-bugs] Issue 18987 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: LRegs.size() == 1 && "Can't handle this yet!"

2019-11-17 Thread ClusterFuzz-External via monorail via llvm-bugs

Status: New
Owner: 
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,  
igm...@gmail.com, d...@google.com, mit...@google.com,  
bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org,  
j...@chromium.org, v...@apple.com, mitchphi...@outlook.com,  
xpl...@gmail.com, akils...@apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-11-17

Type: Bug

New issue 18987 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2:  
ASSERT: LRegs.size() == 1 && "Can't handle this yet!"

https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18987

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

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

Crash Type: ASSERT
Crash Address:
Crash State:
  LRegs.size() == 1 && "Can't handle this yet!"
  ScheduleDAGRRList::PickNodeToScheduleBottomUp
  ScheduleDAGRRList::Schedule

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710160455:201710190451


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


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