[llvm-bugs] Issue 12658 in oss-fuzz: llvm: Build failure
Updates: Status: Verified Comment #3 on issue 12658 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12658#c3 The latest build has succeeded, closing this issue. -- 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 10250 in oss-fuzz: llvm: Build failure
Comment #33 on issue 10250 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10250#c33 Friendly reminder that the the build is still failing. Please try to fix this failure to ensure that fuzzing remains productive. Latest build log: https://oss-fuzz-build-logs.storage.googleapis.com/log-466ef69c-4503-4f4b-98e5-b2e418bff49f.txt -- 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 12846 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: EltTy && "Can't get a pointer to type!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@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-02-02 Type: Bug New issue 12846 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: EltTy && "Can't get a pointer to type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12846 Detailed report: https://oss-fuzz.com/testcase?key=5641756073263104 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-instcombine Fuzz target binary: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: EltTy && "Can't get a pointer to type!" llvm::PointerType::get SimplifyGEPInst Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5641756073263104 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 12848 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@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-02-02 Type: Bug New issue 12848 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12848 Detailed report: https://oss-fuzz.com/testcase?key=5713452666978304 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-gisel Fuzz target binary: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match" llvm::LegalizeRuleSet::apply llvm::LegalizerInfo::getAction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5713452666978304 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 40571] New: Teach LLVM to elide empty static variable guards.
https://bugs.llvm.org/show_bug.cgi?id=40571 Bug ID: 40571 Summary: Teach LLVM to elide empty static variable guards. Product: new-bugs Version: trunk Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: e...@efcs.ca CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org LLVM is great at eliding unneeded initializers and forgetting about trivial destructors, But it doesn't clean up after itself. It leaves empty guarded initialization blocks. For example: https://godbolt.org/z/ONmG22 The [[constinit, no_destroy]] case is particularly frustrating. LLVM should be taught te recognize and remove empty initialization guards. -- 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 40572] New: ICE with C++ module when exporting forward declarations
https://bugs.llvm.org/show_bug.cgi?id=40572 Bug ID: 40572 Summary: ICE with C++ module when exporting forward declarations Product: new-bugs Version: 7.0 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: mjkl...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 21419 --> https://bugs.llvm.org/attachment.cgi?id=21419&action=edit Complete log of build2 verbose build with all commands used. Repro case (using build2): https://github.com/Klaim/clang_modules_ts_ice/ I get an ICE when attempting to compile a C++ module (`clang++ -std=c++2a -D__cpp_modules=201704 -fmodules-ts`, generated using Build2) which content is: export module mystd; #include #include #include #include #include export std::vector; export std::string; export std::variant; export std::type_info; export std::cout; See: https://github.com/Klaim/clang_modules_ts_ice/blob/master/test_clang_ice_module/mystd.mxx Which I believe is incorrect anyway, I get error reports when I remove some of the export lines. Here is the error report: Wrote crash dump file "C:\Users\klaim\AppData\Local\Temp\clang++.exe-85d2ea.dmp" 0x7FF75658E105 (0x008FB258B630 0x7FF75538BF45 0x023E5A5C75A0 0x023E5A5C7568) 0x7FF7C1C2 (0x023E57BA5640 0x 0x023E5A4CC550 0x0016) 0x7FF753DDA5FF (0x023E57B95370 0x023E57BC5F00 0x023E57BC5EF0 0x7FF753DDA161) 0x7FF753DDA213 (0x0400 0x7FF75576A5C3 0x008F 0x7FF70001) 0x7FF754217B28 (0x00110010 0x00130012 0x00150014 0x7FF70016) 0x7FF753DD5EB0 (0x 0x 0xDB1CA2510547 0x023E57BBDAC0) 0x7FF753DDA126 (0x 0x 0x 0x) 0x7FF754D01D1A (0x023E5A16CEC0 0x 0x 0x7FF754DE1E7C) 0x7FF754D9786C (0x008FB258D730 0x 0x023E57C60080 0x7FF754BAB751) 0x7FF754D96CC5 (0xFFF8 0x023E57BD6910 0xFFF8 0x000F) 0x7FF754D95FC2 (0x0003 0x023E57C60080 0x008FB258CD68 0x008FB258DB10) 0x7FF754B5E92C (0x0001 0x023E5A5C6BA8 0x 0x0026D7E9) 0x7FF754B5CDB1 (0x008FB258D740 0x7FF75658C8F0 0x023E59AED788 0x008FB258D720) 0x7FF754B1AF2F (0xDB1CA25117E7 0x023E5A2748E8 0x023E59AED788 0x0003) 0x7FF754B1A900 (0x0026D7E2 0x 0x 0x7FF754DD367A) 0x7FF754B19483 (0x 0x023E57C60090 0x008FB258DD30 0x7FF7555D3744) 0x7FF754B3B55A (0xDB1CA2511B47 0x7FF7555D37EC 0x008FB258DDD0 0x023E59C6D4B0) 0x7FF754B18E1E (0x008FB258DDD0 0x023E57C60080 0x 0x) 0x7FF754B18299 (0x0002 0x008F 0x57AC1401 0x023E57B7D640) 0x7FF754B14BE6 (0x 0x 0x023E57B9AAF0 0x023E57B846D0) 0x7FF75426431D (0x008FB258DEC8 0x7FF756760B08 0x 0x7FF7542BC719) 0x7FF754228CC7 (0x008FB258E101 0x 0x 0x023E57B95F20) 0x7FF7542BD37C (0x023E57BA22D0 0x023E57B4 0x0101 0x7FFB472A) 0x7FF7528C6E28 (0x008FB258F801 0x 0x008FB258 0x7FFB440DF101) 0x7FF7528C4317 (0x 0x 0x 0x) 0x7FF75576A7E8 (0x 0x 0x 0x) 0x7FFB46B97E94 (0x 0x 0x 0x), BaseThreadInitThunk() + 0x14 bytes(s) 0x7FFB4730A251 (0x 0x 0x 0x), RtlUserThreadStart() + 0x21 bytes(s) clang++.exe: error: clang frontend command failed due to signal (use -v to see invocation) clang version 7.0.1 (tags/RELEASE_701/final) Target: x86_64-pc-windows-msvc Thread model: posix InstalledDir: C:\Program Files\LLVM\bin clang++.exe: note: diagnostic msg: PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script. clang++.exe: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang++.exe: note: diagnostic msg: C:\Users\klaim\AppData\Local\Temp\mystd-2c3bd9.cppm clang++.exe: note: diagnostic msg: C:\Users\klaim\AppData\Local\Temp\mystd-2c3bd9.sh clang++.exe: note: d
[llvm-bugs] Issue 12437 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!"
Comment #3 on issue 12437 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12437#c3 ClusterFuzz has detected this issue as fixed in range 201901220414:201902020421. Detailed report: https://oss-fuzz.com/testcase?key=5763030103621632 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--wasm32-O2 Fuzz target binary: llvm-isel-fuzzer--wasm32-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!" llvm::DAGTypeLegalizer::SplitVecOp_EXTRACT_VECTOR_ELT llvm::DAGTypeLegalizer::SplitVectorOperand Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201808290128:201808300127 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5763030103621632 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 12437 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 12437 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--wasm32-O2: ASSERT: IdxVal < VecVT.getVectorNumElements() && "Invalid vector index!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12437#c4 ClusterFuzz testcase 5763030103621632 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 12548 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Comment #1 on issue 12548 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12548#c1 ClusterFuzz has detected this issue as fixed in range 201901220414:201902020421. Detailed report: https://oss-fuzz.com/testcase?key=5758665628319744 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: 0x7ffeb51f5cc8 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=201801030610:201801040618 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5758665628319744 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 12730 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
Comment #1 on issue 12730 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12730#c1 ClusterFuzz has detected this issue as fixed in range 201901220414:201902020421. Detailed report: https://oss-fuzz.com/testcase?key=5661316369350656 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: 0x7ffd55ef8a08 Crash State: clang::FunctionProtoType::getExtProtoInfo clang::FunctionProtoType::Profile llvm::ContextualFoldingSetclang::ASTContext&>::NodeEq Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201807110801:201807230239 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5661316369350656 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 12397 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?"
Comment #2 on issue 12397 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12397#c2 ClusterFuzz has detected this issue as fixed in range 201901220414:201902020421. Detailed report: https://oss-fuzz.com/testcase?key=5640809326575616 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-earlycse Fuzz target binary: llvm-opt-fuzzer--x86_64-earlycse Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !FoundVal && "Key already in new map?" llvm::DenseMapBasellvm::ScopedHashTableVal llvm::DenseMapBasellvm::ScopedHashTableVal Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812100233:201812110234 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5640809326575616 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 9579 in oss-fuzz: llvm/clangd-fuzzer: Stack-overflow in llvm::json::Parser::parseValue
Comment #3 on issue 9579 by ClusterFuzz-External: llvm/clangd-fuzzer: Stack-overflow in llvm::json::Parser::parseValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9579#c3 ClusterFuzz has detected this issue as fixed in range 201901220414:201902020421. Detailed report: https://oss-fuzz.com/testcase?key=5665609932079104 Project: llvm Fuzzer: libFuzzer_llvm_clangd-fuzzer Fuzz target binary: clangd-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffca1a63c38 Crash State: llvm::json::Parser::parseValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201807090754:201807110151 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5665609932079104 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 12515 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Comment #1 on issue 12515 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12515#c1 ClusterFuzz has detected this issue as fixed in range 201901220414:201902020421. Detailed report: https://oss-fuzz.com/testcase?key=5730972266397696 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: 0x7ffd661f1e48 Crash State: clang::DiagnosticIDs::isUnrecoverable clang::DiagnosticIDs::ProcessDiag clang::DiagnosticsEngine::EmitCurrentDiagnostic Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901100404:201901120423 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5730972266397696 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 12511 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in ConvertDeclSpecToType
Comment #1 on issue 12511 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in ConvertDeclSpecToType https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12511#c1 ClusterFuzz has detected this issue as fixed in range 201901220414:201902020421. Detailed report: https://oss-fuzz.com/testcase?key=5730540622184448 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: 0x7ffeb45bfcf8 Crash State: ConvertDeclSpecToType GetDeclSpecTypeForDeclarator clang::Sema::GetTypeForDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901100404:201901120423 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5730540622184448 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 12397 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 12397 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12397#c3 ClusterFuzz testcase 5640809326575616 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 12730 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 12730 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12730#c2 ClusterFuzz testcase 5661316369350656 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 9579 in oss-fuzz: llvm/clangd-fuzzer: Stack-overflow in llvm::json::Parser::parseValue
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 9579 by ClusterFuzz-External: llvm/clangd-fuzzer: Stack-overflow in llvm::json::Parser::parseValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9579#c4 ClusterFuzz testcase 5665609932079104 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 12515 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 12515 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12515#c2 ClusterFuzz testcase 5730972266397696 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 12511 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in ConvertDeclSpecToType
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 12511 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in ConvertDeclSpecToType https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12511#c2 ClusterFuzz testcase 5730540622184448 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 12548 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 12548 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12548#c2 ClusterFuzz testcase 5758665628319744 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] [Bug 40573] New: [Debuginfo] @llvm.dbg.value changes behaviour of "Speculatively execute instructions"
https://bugs.llvm.org/show_bug.cgi?id=40573 Bug ID: 40573 Summary: [Debuginfo] @llvm.dbg.value changes behaviour of "Speculatively execute instructions" Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Scalar Optimizations Assignee: unassignedb...@nondot.org Reporter: pauls...@linux.vnet.ibm.com CC: llvm-bugs@lists.llvm.org Created attachment 21421 --> https://bugs.llvm.org/attachment.cgi?id=21421&action=edit reduced testcase Without the @llvm.dbg instruction in the test case, the fdiv instruction is moved up in the CFG by bin/opt -mtriple=systemz-unknown -mcpu=z13 -S tc_speculexe.ll -speculative-execution I suspect that this is also (as in bug 40564) related to counting instructions in the block on the line if (NotHoisted.size() > SpecExecMaxNotHoisted) in SpeculativeExecution.cpp -- 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 10380 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::CachingLex
Comment #4 on issue 10380 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::CachingLex https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10380#c4 ClusterFuzz has detected this issue as fixed in range 201901220414:201902020421. Detailed report: https://oss-fuzz.com/testcase?key=5696472863997952 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: 0x7ffe2342fee8 Crash State: clang::Preprocessor::CachingLex clang::Preprocessor::Lex clang::Parser::ParseParenExpression Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201806260706:201806270010 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5696472863997952 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 10380 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::CachingLex
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #5 on issue 10380 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::CachingLex https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10380#c5 ClusterFuzz testcase 5696472863997952 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] [Bug 40574] New: Field ordering still causes extra memcpy
https://bugs.llvm.org/show_bug.cgi?id=40574
Bug ID: 40574
Summary: Field ordering still causes extra memcpy
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: jmuizel...@mozilla.com
CC: llvm-bugs@lists.llvm.org
Even with bug 39844 fixed we can still get extra memcpys depending on field
ordering:
#include
struct SV {
size_t capacity;
size_t disc;
size_t data[40];
static SV make() {
SV ret;
ret.capacity = 0;
ret.disc = 0;
return ret;
}
};
struct L {
SV a;
SV b;
};
template
struct Allocation {
T *vec;
void init(T s) {
*vec = s;
}
};
void bar(Allocation a, double g) {
L s = { SV::make(), SV::make() };
a.init(s);
}
produces
bar(Allocation, double):# @bar(Allocation, double)
subq$680, %rsp # imm = 0x2A8
xorps %xmm0, %xmm0
movaps %xmm0, (%rsp)
movaps %xmm0, 336(%rsp)
movq%rsp, %rsi
movl$672, %edx # imm = 0x2A0
callq memcpy
addq$680, %rsp # imm = 0x2A8
retq
but moving capacity to the end gives:
bar(Allocation, double):# @bar(Allocation, double)
movq$0, (%rdi)
xorps %xmm0, %xmm0
movups %xmm0, 328(%rdi)
movq$0, 664(%rdi)
retq
--
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 40575] New: std::copy to memmove optimisation seems to not work.
https://bugs.llvm.org/show_bug.cgi?id=40575 Bug ID: 40575 Summary: std::copy to memmove optimisation seems to not work. Product: libc++ Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: denis.yaroshevs...@gmail.com CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com std::copy has an optimization to memmove but it doesn't seem to work: https://gcc.godbolt.org/z/a6lvSm (no memmove) I has real consequences: libstdc++: http://quick-bench.com/vpLxYCWfverSzlWxFjwuXxELD8Q libc++: http://quick-bench.com/kfsPjkSo79hHiy0ZVrMCn7wU6Xw -- 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 40576] New: Clang should turn destroying delete off by default.
https://bugs.llvm.org/show_bug.cgi?id=40576 Bug ID: 40576 Summary: Clang should turn destroying delete off by default. Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: normal Priority: P Component: C++2a Assignee: unassignedclangb...@nondot.org Reporter: e...@efcs.ca CC: blitzrak...@gmail.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Defining new names in namespace `std` is technically a non-conforming extensions. This makes it difficult for libc++ to backport C++20 destroying delete. Currently Clang unconditionally defines `__cpp_impl_destroying_delete`. Unlike aligned allocation or sized deallocation which can be turned on or off by user. I believe we should make destroying delete act similarly. We should provide flags for enabling destroying delete prior to C++17. After `__cpp_impl_destroying_delete` should be defined by default. Lets also consider whether Clang should provide destroying delete as an extension prior to C++20. PS. I'm concerned that if Clang always provides destroying delete but libc++ doesn't define it until C++20, then users will be dinks and define their own `std::destroying_delete_t` as a workaround. -- 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 12857 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: Val && "isa<> used on a null pointer"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@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-02-03 Type: Bug New issue 12857 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-instcombine: ASSERT: Val && "isa<> used on a null pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12857 Detailed report: https://oss-fuzz.com/testcase?key=5667767804493824 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-instcombine Fuzz target binary: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Val && "isa<> used on a null pointer" computeKnownBitsFromOperator computeKnownBits Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5667767804493824 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 40577] New: [clang-cl] [ms] Implement warning for shadowing of template parameter extension
https://bugs.llvm.org/show_bug.cgi?id=40577
Bug ID: 40577
Summary: [clang-cl] [ms] Implement warning for shadowing of
template parameter extension
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: heavenandhell...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
Clang usually warns whenever it compiles non conformant code that MSVC accepts,
which i think it's great. However, there is no warning for shadowing of
template parameters, which is illegal.
For exemple:
$ cat test.cpp
template
struct type_t {
template
void function() {
}
};
$ clang-cl -c test.cpp
No warning.
I discovered that this is ill-formed when i pushed some code and the GCC build
bot failed. It would be nice to have Clang warn about this extension.
Something like:
$ clang-cl -c test.cpp
test.cpp(3,22): warning: declaration of 'T' shadows template parameter;
ignored as a Microsoft extension
[-Wmicrosoft-template]
template
^
test.cpp(1,20): note: template parameter is declared here
template
^
1 warning generated.
--
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 35706] Missed optimization in math expression: log10(pow(10.0, x)) == x
https://bugs.llvm.org/show_bug.cgi?id=35706 Dmitry Venikov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Dmitry Venikov --- rL352981 -- 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 35611] [meta] Missed fast-math optimizations
https://bugs.llvm.org/show_bug.cgi?id=35611 Bug 35611 depends on bug 35706, which changed state. Bug 35706 Summary: Missed optimization in math expression: log10(pow(10.0,x)) == x https://bugs.llvm.org/show_bug.cgi?id=35706 What|Removed |Added Status|CONFIRMED |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
