[llvm-bugs] [Bug 44130] New: Backport fix for lld build failure to 9.0
https://bugs.llvm.org/show_bug.cgi?id=44130 Bug ID: 44130 Summary: Backport fix for lld build failure to 9.0 Product: new-bugs Version: 9.0 Hardware: PC OS: other Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: aykevanlaet...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Blocks: 43360 I would like to see this revision merged in the 9.0 branch. The 9.0 branch of lld cannot be compiled with MinGW 8 (and up?) and needs the following fix to get it to compile again: https://reviews.llvm.org/D70266 Note that there is a small difference between the Differential revision and the committed change (https://reviews.llvm.org/rG57776f71fa32a5b170a9ce82cb2c2da0a207908c): the Differential revision was made for the 9.0 branch but didn't apply directly to master (hence the difference). For the 9.0 branch, the Differential patch should be applied. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=43360 [Bug 43360] [meta] 9.0.1 Release Blockers -- 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 44131] New: DenseMap segfaults due to (de)allocate_buffer incompatibility with C++17 host application.
https://bugs.llvm.org/show_bug.cgi?id=44131 Bug ID: 44131 Summary: DenseMap segfaults due to (de)allocate_buffer incompatibility with C++17 host application. Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: release blocker Priority: P Component: Support Libraries Assignee: unassignedb...@nondot.org Reporter: jc...@machiel.info CC: llvm-bugs@lists.llvm.org I have a C++17 Windows/MSVC host application that uses the llvm libraries compiled with C++14. My application segfaults when running a release build due to how allocate_buffer and deallocate_buffer are implemented. In those functions, #ifdef __cpp_aligned_new is used to test for the aligned_new feature which is present in C++17 but not in C++14. Because these functions are defined in a header file (Compiler.h) this will introduce an incompatibility when buffers are allocated by some llvm function and freed by some function that eventually calls deallocate_buffer from my host application. Buffers will be allocated without a specific alignment and then potentially de-allocated with the aligned version of operator delete or vice versa. Commenting those #ifdefs out fixes it for me. Those function should either be implemented in a .cpp file or those #ifdefs should use some #define that is defined at llvm library compile time instead of using __cpp_aligned_new. -- 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 19085 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in HasAccess
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2019-11-24 Type: Bug-Security New issue 19085 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in HasAccess https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19085 Detailed Report: https://oss-fuzz.com/testcase?key=5740402812649472 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Segv on unknown address Crash Address: Crash State: HasAccess IsAccessible CheckEffectiveAccess Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=201911200438:201911230451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5740402812649472 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19086 in oss-fuzz: llvm:clang-objc-fuzzer: Segv on unknown address in clang::ObjCMethodDecl::getOverriddenMethods
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2019-11-24 Type: Bug-Security New issue 19086 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Segv on unknown address in clang::ObjCMethodDecl::getOverriddenMethods https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19086 Detailed Report: https://oss-fuzz.com/testcase?key=5745806737145856 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Segv on unknown address Crash Address: Crash State: clang::ObjCMethodDecl::getOverriddenMethods clang::ObjCMethodDecl::findPropertyDecl clang::Sema::DiagnoseUseOfDecl Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=201911200438:201911230451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5745806737145856 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19088 in oss-fuzz: llvm:clang-objc-fuzzer: Segv on unknown address in clang::Parser::ParseObjCInterfaceDeclList
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2019-11-25 Type: Bug-Security New issue 19088 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Segv on unknown address in clang::Parser::ParseObjCInterfaceDeclList https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19088 Detailed Report: https://oss-fuzz.com/testcase?key=5696539704164352 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-objc-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Segv on unknown address Crash Address: Crash State: clang::Parser::ParseObjCInterfaceDeclList clang::Parser::ParseObjCAtInterfaceDeclaration clang::Parser::ParseObjCAtDirectives Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=201911200438:201911230451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5696539704164352 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 19089 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in processTypeAttrs
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-11-25 Type: Bug New issue 19089 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in processTypeAttrs https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19089 Detailed Report: https://oss-fuzz.com/testcase?key=5735260310732800 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd24aa4da0 Crash State: processTypeAttrs ConvertDeclSpecToType GetDeclSpecTypeForDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201911200438:201911230451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5735260310732800 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
