[llvm-bugs] Issue 7560 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: Heap-use-after-free in llvm::LoopVectorizationCostModel::setCostBasedWideningDecision
Comment #11 on issue 7560 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: Heap-use-after-free in llvm::LoopVectorizationCostModel::setCostBasedWideningDecision https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7560#c11 ClusterFuzz has detected this issue as fixed in range 201903070433:201903090441. Detailed report: https://oss-fuzz.com/testcase?key=5746655065276416 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_vectorize Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_vectorize Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Heap-use-after-free READ 4 Crash Address: 0x608124e0 Crash State: llvm::LoopVectorizationCostModel::setCostBasedWideningDecision llvm::LoopVectorizationCostModel::collectUniformsAndScalars llvm::LoopVectorizationPlanner::plan Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802190622:201802200626 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903070433:201903090441 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5746655065276416 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. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13229 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !getMember(0)->mayWriteToMemory() && "Group should have been invalidated"
Comment #2 on issue 13229 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !getMember(0)->mayWriteToMemory() && "Group should have been invalidated" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13229#c2 ClusterFuzz has detected this issue as fixed in range 201903070433:201903090441. Detailed report: https://oss-fuzz.com/testcase?key=5713358093811712 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_vectorize Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_vectorize Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !getMember(0)->mayWriteToMemory() && "Group should have been invalidated" llvm::LoopVectorizationCostModel::interleavedAccessCanBeWidened llvm::LoopVectorizationCostModel::setCostBasedWideningDecision Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201810170227:20181623 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903070433:201903090441 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5713358093811712 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. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13128 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: WideningDecision != CM_Unknown && "Widening decision should be ready at this mom
Comment #2 on issue 13128 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: WideningDecision != CM_Unknown && "Widening decision should be ready at this mom https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13128#c2 ClusterFuzz has detected this issue as fixed in range 201903070433:201903090441. Detailed report: https://oss-fuzz.com/testcase?key=5754785267974144 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_vectorize Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_vectorize Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: WideningDecision != CM_Unknown && "Widening decision should be ready at this mom llvm::LoopVectorizationCostModel::collectLoopScalars llvm::LoopVectorizationCostModel::collectLoopScalars Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201810160226:201810170227 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903070433:201903090441 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5754785267974144 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. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13499 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Comment #1 on issue 13499 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13499#c1 ClusterFuzz has detected this issue as fixed in range 201903070433:201903090441. Detailed report: https://oss-fuzz.com/testcase?key=5698428825239552 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd21cf1f28 Crash State: llvm::StringMapImpl::LookupBucketFor std::__1::pair, bool> llvm::Stri clang::Preprocessor::LookUpIdentifierInfo Sanitizer: address (ASAN) Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903070433:201903090441 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5698428825239552 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. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13499 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 13499 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13499#c2 ClusterFuzz testcase 5698428825239552 is verified as fixed, so closing issue as verified. 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 13229 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !getMember(0)->mayWriteToMemory() && "Group should have been invalidated"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 13229 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: !getMember(0)->mayWriteToMemory() && "Group should have been invalidated" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13229#c3 ClusterFuzz testcase 5713358093811712 is verified as fixed, so closing issue as verified. 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 7560 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: Heap-use-after-free in llvm::LoopVectorizationCostModel::setCostBasedWideningDecision
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #12 on issue 7560 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: Heap-use-after-free in llvm::LoopVectorizationCostModel::setCostBasedWideningDecision https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7560#c12 ClusterFuzz testcase 5746655065276416 is verified as fixed, so closing issue as verified. 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 13128 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: WideningDecision != CM_Unknown && "Widening decision should be ready at this mom
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 13128 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_vectorize: ASSERT: WideningDecision != CM_Unknown && "Widening decision should be ready at this mom https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13128#c3 ClusterFuzz testcase 5754785267974144 is verified as fixed, so closing issue as verified. 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 13630 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: MRI->getVRegDef(Reg) && "Machine instr not mapped for this vreg?!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.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 Proj-llvm Reported-2019-03-09 Type: Bug New issue 13630 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: MRI->getVRegDef(Reg) && "Machine instr not mapped for this vreg?!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13630 Detailed report: https://oss-fuzz.com/testcase?key=5647237177147392 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: MRI->getVRegDef(Reg) && "Machine instr not mapped for this vreg?!" MachineLICMBase::IsLoopInvariantInst MachineLICMBase::runOnMachineFunction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903050442:201903070433 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5647237177147392 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md 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. -- 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 13631 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: use_empty() && "Uses remain when a value is destroyed!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.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 Proj-llvm Reported-2019-03-09 Type: Bug New issue 13631 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: use_empty() && "Uses remain when a value is destroyed!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13631 Detailed report: https://oss-fuzz.com/testcase?key=5658096699965440 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: use_empty() && "Uses remain when a value is destroyed!" llvm::Value::~Value llvm::Value::deleteValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903050442:201903070433 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5658096699965440 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md 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. -- 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 13639 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Direct-leak in llvm::Value::setNameImpl
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.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 Stability-Memory-LeakSanitizer Engine-libfuzzer Proj-llvm Reported-2019-03-09 Type: Bug New issue 13639 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-strength_reduce: Direct-leak in llvm::Value::setNameImpl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13639 Detailed report: https://oss-fuzz.com/testcase?key=5765912626462720 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-strength_reduce Fuzz target binary: llvm-opt-fuzzer--x86_64-strength_reduce Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Direct-leak Crash Address: Crash State: llvm::Value::setNameImpl llvm::Value::setName BitcodeReader::recordValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802210603:201802211531 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5765912626462720 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md 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. -- 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] [Bug 41019] New: Incorrectly warning about nullable parameter
https://bugs.llvm.org/show_bug.cgi?id=41019 Bug ID: 41019 Summary: Incorrectly warning about nullable parameter Product: clang Version: trunk Hardware: Macintosh OS: MacOS X Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: alexbrachetmia...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Seems to be a bug around nullability. attr argument to pthread_mutex_init is declared _Nullable in the header on my machine but clang still complains to me when passing NULL. Not a huge bug but it is annoying. int pthread_mutex_init(pthread_mutex_t * __restrict, const pthread_mutexattr_t * _Nullable __restrict); thpool.c:37:47: warning: null passed to a callee that requires a non-null argument [-Wnonnull] (void) pthread_mutex_init(&tp->mutex, NULL); ^ -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40442] [SelectionDAG] Enable ISD::SADDO/SSUBO/SMULO/UADDO/USUBO/UMULO vector support
https://bugs.llvm.org/show_bug.cgi?id=40442 Nikita Popov changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Nikita Popov --- Nope, I think we got everything here :) -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37763] [X86] Investigate vectorization of the overflow add/sub nodes to PADD+PADDS+PCMPEQ etc.
https://bugs.llvm.org/show_bug.cgi?id=37763 Bug 37763 depends on bug 40442, which changed state. Bug 40442 Summary: [SelectionDAG] Enable ISD::SADDO/SSUBO/SMULO/UADDO/USUBO/UMULO vector support https://bugs.llvm.org/show_bug.cgi?id=40442 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 13641 in oss-fuzz: llvm/clang-fuzzer: ASSERT: isa(Val) && "cast() argument of incompatible type!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.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 Proj-llvm Reported-2019-03-10 Type: Bug New issue 13641 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: isa(Val) && "cast() argument of incompatible type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13641 Detailed report: https://oss-fuzz.com/testcase?key=6196881187667968 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: isa(Val) && "cast() argument of incompatible type!" clang::OverloadExpr::find clang::Sema::ResolveAndFixSingleFunctionTemplateSpecialization Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902140416:201902150428 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6196881187667968 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md 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. -- 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
