[llvm-bugs] 5 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the reproducibility label flip to Unreproducible. This was an infrastructure issue that is now resolved. Switching the labels back, sorry for the inconvenience. Affected issues: issue 10821: llvm/clang-fuzzer: Stack-overflow in EvaluateValue http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10821 issue 11885: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11885 issue 12433: llvm/llvm-itanium-demangle-fuzzer: Timeout in llvm_llvm-itanium-demangle-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12433 issue 12439: llvm/llvm-itanium-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12439 issue 12898: llvm/clangd-fuzzer: Stack-overflow in llvm::json::Parser::parseValue http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12898 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 16251 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Unexpected-exit in MSanAtExitWrapper
Updates: Status: WontFix Comment #1 on issue 16251 by infe...@chromium.org: llvm/llvm-dwarfdump-fuzzer: Unexpected-exit in MSanAtExitWrapper https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16251#c1 MSanAtExitWrapper frame is blacklisted, but this is valid bug. we will wait for another testcase to get created. -- 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 12897 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray
Comment #5 on issue 12897 by infe...@chromium.org: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12897#c5 Can you try accessing it again. -- 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] 4 issues changed in oss-fuzz
Updates: Status: New Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 4125: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4125 issue 4176: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in llvm_regcomp http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4176 issue 4192: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4192 issue 7560: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: Heap-use-after-free in llvm::LoopVectorizationCostModel::setCostBasedWideningDecision http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7560 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 5 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 4748: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: i < ValuePtrs.size() http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4748 issue 6158: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: RC && "This value type is not natively supported!" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6158 issue 6527: llvm/clang-fuzzer: Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6527 issue 8294: llvm/clang-fuzzer: ASSERT: !LHS.get()->getType()->isPlaceholderType() && !RHS.get()->getType()->isPlacehold http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8294 issue 9142: llvm/llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: i < getNumArgOperands() && "Out of bounds!" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9142 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 15 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 3133: llvm: ASSERT: DelayedTypos.empty() && "Uncorrected typos!" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3133 issue 3155: llvm: ASSERT: CachedTokens[CachedLexPos-1].getLastLoc() == Tok.getAnnotationEndLoc() && "The a http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3155 issue 3239: llvm: ASSERT: getContainingDC(DC) == CurContext && "The next DeclContext should be lexically c http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3239 issue 3264: llvm: ASSERT: Ancestor->getEntity() == CurContext && "ancestor context mismatch" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3264 issue 3353: llvm: ASSERT: CodeDC && !CodeDC->isFileContext() && "statement expr not in code context" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3353 issue 3676: llvm/clang-format-fuzzer: ASSERT: PPBranchLevel < (int)PPLevelBranchIndex.size() http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3676 issue 3737: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3737 issue 4558: llvm/clang-format-fuzzer: ASSERT: NewRemainingTokenColumns < RemainingTokenColumns http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4558 issue 4766: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: EltSize * 8 == EltVT.getSizeInBits() && "Converting bits to bytes lost precision http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4766 issue 6057: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: !carry http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6057 issue 6592: llvm/llvm-opt-fuzzer--x86_64-loop_unswitch: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-loop_unswitch http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6592 issue 7689: llvm/llvm-demangle-fuzzer: Out-of-memory in llvm_llvm-demangle-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7689 issue 10631: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: (!RS | | !RS->isScavengingFrameIndex(FrameIndex)) && "Emergency spill slot is out http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10631 issue 10883: llvm/llvm-isel-fuzzer--aarch64-gisel: Null-dereference READ in llvm::AArch64RegisterBankInfo::getInstrMapping http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10883 issue 11046: llvm/llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm_llvm-opt-fuzzer--x86_64-indvars http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11046 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 4 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 4656: llvm/clang-fuzzer: Out-of-memory in llvm_clang-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4656 issue 6893: llvm/llvm-opt-fuzzer--x86_64-sccp: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-sccp http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6893 issue 10075: llvm/clang-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10075 issue 10907: llvm/clang-format-fuzzer: Timeout in llvm_clang-format-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10907 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 4 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 4081: llvm/clang-format-fuzzer: ASSERT: idx < size() http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4081 issue 4737: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: idx < size() http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4737 issue 5455: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: New->getType() == getType() && "replaceAllUses of value with new value of differ http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5455 issue 11234: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in llvm_llvm-opt-fuzzer--x86_64-strength_reduce http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11234 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 4 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 11423: llvm/llvm-special-case-list-fuzzer: Timeout in llvm_llvm-special-case-list-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11423 issue 11555: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ShiftAmt <= BitWidth && "Invalid shift amount" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11555 issue 11567: llvm/clang-fuzzer: Null-dereference READ in diagnoseBadTypeAttribute http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11567 issue 11593: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::DWARFFormValue::dump http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11593 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 6 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 4714: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: Offset <= INT_MAX && "Offset too big to fit in int." http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4714 issue 9418: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: (VTy->isFirstClassType() || VTy->isVoidTy()) && "Cannot create non-first-class v http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9418 issue 10980: llvm/llvm-special-case-list-fuzzer: Out-of-memory in llvm_llvm-special-case-list-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10980 issue 11023: llvm/clang-fuzzer: Timeout in llvm_clang-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11023 issue 11075: llvm/llvm-dwarfdump-fuzzer: Timeout in llvm_llvm-dwarfdump-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11075 issue 11363: llvm/llvm-demangle-fuzzer: Stack-overflow in llvm::itanium_demangle::AbstractManglingParser http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11363 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 3 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 4702: llvm/llvm-isel-fuzzer--aarch64-gisel: Direct-leak in llvm::BitcodeReaderValueList::getValueFwdRef http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4702 issue 4712: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: TRI.getRegSizeInBits(*getRegClass(DstReg)) == TRI.getRegSizeInBits(*getRegClass( http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4712 issue 4858: llvm/clang-fuzzer: Abrt in llvm::llvm_unreachable_internal http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4858 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 6 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications. Affected issues: issue 7690: llvm/llvm-opt-fuzzer--x86_64-licm: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-licm http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7690 issue 8605: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: (Known.Zero & Known.One) == 0 && "Bits known to be one AND zero?" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8605 issue 8694: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::object::ELFObjectFile http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8694 issue 8699: llvm/llvm-dwarfdump-fuzzer: Out-of-memory in llvm_llvm-dwarfdump-fuzzer http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8699 issue 8819: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: E <= size() && "Attempted to reset out-of-bounds range!" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8819 issue 9569: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::report_bad_alloc_error http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9569 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 10 issues changed in oss-fuzz
Updates: Labels: -Unreproducible Reproducible Comment by infe...@chromium.org: Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Affected issues: issue 4125: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4125 issue 4176: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in llvm_regcomp http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4176 issue 4574: llvm/clang-fuzzer: ASSERT: !E->isArrow() && "missing call to bound member function?" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4574 issue 4604: llvm/clang-fuzzer: ASSERT: (data().DefaultedCopyConstructorIsDeleted || needsOverloadResolutionForCopyConst http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4604 issue 6052: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: ID < (MDStringRef.size()) + GlobalMetadataBitPosIndex.size() http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6052 issue 6415: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: (DestReg != AArch64::SP || Offset % 16 == 0) && "SP increment/decrement not 16-b http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6415 issue 7167: llvm/llvm-dwarfdump-fuzzer: Abrt in llvm::llvm_unreachable_internal http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7167 issue 7177: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: getMinSignedBits() <= 64 && "Too many bits for int64_t" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7177 issue 7701: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: isa(Val) && "cast() argument of incompatible type!" http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7701 issue 8037: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in llvm::llvm_unreachable_internal http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8037 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://bugs.chromium.org/hosting/settings ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] 30 issues changed in oss-fuzz
Updates:
Labels: -Unreproducible Reproducible
Comment by infe...@chromium.org:
Please ignore the last comment about testcase being unreproducible. The
testcase is still reproducible. This happened due to a code refactoring on
ClusterFuzz side, and the underlying root cause is now fixed. Resetting the
label back to Reproducible.
Affected issues:
issue 3146: llvm: ASSERT: Access != AS_none && "Access specifier is
AS_none inside a record decl"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3146
issue 3163: llvm: ASSERT: Tok.is(tok::eof) && Tok.getEofData() ==
AttrEnd.getEofData()
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3163
issue 3168: llvm: ASSERT: Access == AS_private || Access == AS_protected
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3168
issue 3169: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3169
issue 3171: llvm: ASSERT: RHS.U.VAL != 0 && "Divide by zero?"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3171
issue 3178: llvm: ASSERT: !CodeSynthesisContexts.empty()
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3178
issue 3194: llvm: Abrt in llvm::llvm_unreachable_internal
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3194
issue 3369: llvm: Out-of-memory in llvm_clang-format-fuzzer
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3369
issue 3370: llvm: ASSERT: getClient() && "DiagnosticClient not set!"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3370
issue 3705: llvm/clang-fuzzer: ASSERT: getResultKind() == Found
&& "getFoundDecl called on non-unique result"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3705
issue 3979: llvm/clang-fuzzer: ASSERT: !isNull() && "Cannot retrieve a
NULL type pointer"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3979
issue 4063: llvm/clang-fuzzer: ASSERT: isa(Val) && "cast()
argument of incompatible type!"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4063
issue 4192: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in
p_ere
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4192
issue 4278: llvm/clang-format-fuzzer: ASSERT: (TokenText.startswith("//")
|| TokenText.startswith("#")) && "unsupported line c
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4278
issue 4575: llvm/clang-fuzzer: ASSERT: DD && "queried property of class
with no definition"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4575
issue 4608: llvm/clang-fuzzer: Stack-overflow in
clang::Parser::ParseDeclaratorInternal
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4608
issue 4701: llvm/llvm-isel-fuzzer--x86_64-O2: Direct-leak in
llvm::MDTuple::getImpl
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4701
issue 4704: llvm/llvm-isel-fuzzer--aarch64-gisel: Abrt in
handleLLVMFatalError
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4704
issue 4706: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: VSTOffset
== 0 || !F->hasName()
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4706
issue 4740: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in
llvm::llvm_unreachable_internal
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4740
issue 4755: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT:
I.use_empty() && "Cannot erase instruction that is used!"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4755
issue 4978: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: NumBytes >= 0
&& "Negative stack allocation size!?"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4978
issue 4988: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in
llvm::llvm_unreachable_internal
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4988
issue 5250: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ((OffsetImm & 1)
== 0) && "Unexpected offset to merge"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5250
issue 5426: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT:
N->getOpcode() != ISD::DELETED_NODE && "DELETED_NODE in CSEMap!"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5426
issue 5446: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: getMinSignedBits()
<= 64 && "Too many bits for int64_t"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5446
issue 5779: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: fs == opOK ||
fs == opInexact
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5779
issue 6109: llvm/llvm-opt-fuzzer--x86_64-sccp: ASSERT: getActiveBits() <=
64 && "Too many bits for uint64_t"
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6109
issue 6477: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT:
VPlans.size() == 1 && "Best VF has not a single VPlan."
http://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6477
issue 6674: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT:
