[llvm-bugs] Issue 4778 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
Comment #3 on issue 4778 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::StmtVisitorBaseIntExprEvaluator, bool>::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4778#c3 ClusterFuzz has detected this issue as fixed in range 201801130619:201801140616. Detailed report: https://oss-fuzz.com/testcase?key=5083207931265024 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: 0x7ffd34c19f00 Crash State: clang::StmtVisitorBasebool>::Visit Evaluate IntExprEvaluator::VisitUnaryOperator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711140614:201711141648 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801130619:201801140616 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5083207931265024 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 4778 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::StmtVisitorBase::Visit
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 4778 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::StmtVisitorBaseIntExprEvaluator, bool>::Visit https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4778#c4 ClusterFuzz testcase 5083207931265024 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 12961] attached testcase compiles in c++ mode, but not in c++11 mode
https://bugs.llvm.org/show_bug.cgi?id=12961 Roman Lebedev changed: What|Removed |Added Resolution|--- |FIXED CC||lebedev...@gmail.com Status|NEW |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 21629] Warning "missing braces around initializer" causing problems with std::array
https://bugs.llvm.org/show_bug.cgi?id=21629 Nico Weber changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED CC||nicolaswe...@gmx.de --- Comment #10 from Nico Weber --- Sounds like this is done. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35944] incorrect weak-vtables warning on abstract base class
https://bugs.llvm.org/show_bug.cgi?id=35944 Christian Maaser changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Christian Maaser --- The reason for this warning seems to be that a pure virtual destructor's definition cannot be key function for where to place the vtable. See https://stackoverflow.com/questions/28786473/clang-no-out-of-line-virtual-method-definitions-pure-abstract-c-class/40550578 and http://clang.llvm.org/doxygen/classclang_1_1ASTContext.html#a439522ed0cae62952acae5f30f283de2 > NOTE: In the abstract, a pure virtual destructor could be used as the key > function, as it must be defined even though it is pure. However, the ABI > committee did not realize this fact until after the specification of key > function was complete; therefore a pure virtual destructor cannot be the > key function. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5303 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: BaseReg == nullptr
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-14 Type: Bug New issue 5303 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: BaseReg == nullptr https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5303 Detailed report: https://oss-fuzz.com/testcase?key=4575078260932608 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: BaseReg == nullptr CodeGenPrepare::optimizeMemoryInst CodeGenPrepare::optimizeInst Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801120612:201801130619 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4575078260932608 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35843] Assertion in APInt::getSExtValue in -aa-eval
https://bugs.llvm.org/show_bug.cgi?id=35843 Davide Italiano changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Davide Italiano --- r322467 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5308 in oss-fuzz: llvm: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-01-15 Type: Bug New issue 5308 by ClusterFuzz-External: llvm: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5308 Detailed report: https://oss-fuzz.com/testcase?key=6129584899620864 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fffe9754aa8 Crash State: llvm::StringMapImpl::LookupBucketFor std::__1::pair, bool> llvm::Stri clang::Preprocessor::LookUpIdentifierInfo Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801110649:201801120612 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6129584899620864 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. 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 have questions for the OSS-Fuzz team, 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35382] No matching function for call to RegisterTarget
https://bugs.llvm.org/show_bug.cgi?id=35382 Kaushik Phatak changed: What|Removed |Added Status|NEW |RESOLVED CC||kpha...@gmail.com Resolution|--- |FIXED --- Comment #3 from Kaushik Phatak --- This is fixed in r318895 by a patch from Leslie Zhai. Setting this to resolved. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35899] -globals-aa affected by dbg intrinsic leading to different code after instcombine
https://bugs.llvm.org/show_bug.cgi?id=35899 Mikael Holmén changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Mikael Holmén --- (In reply to Mikael Holmén from comment #1) > I created a patch that solves the problem but I don't know if it should be > fixed in some ther way or not: > https://reviews.llvm.org/D41984 Pushed in rL322470. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
