[llvm-bugs] [Bug 40005] Don't overwrite the OS/ABI and ABIVERSION fields of the ELF header
https://bugs.llvm.org/show_bug.cgi?id=40005 George Rimar changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from George Rimar --- r349741 -- 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 12103 in oss-fuzz: llvm/llvm-isel-fuzzer--wasm32-O2: Out-of-memory in llvm-isel-fuzzer--wasm32-O2
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 Reproducible Engine-libfuzzer Proj-llvm Reported-2018-12-21 Type: Bug New issue 12103 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--wasm32-O2: Out-of-memory in llvm-isel-fuzzer--wasm32-O2 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12103 Detailed report: https://oss-fuzz.com/testcase?key=5701986146582528 Project: llvm Fuzzer: libFuzzer_llvm-isel-fuzzer--wasm32-O2 Fuzz target binary: llvm-isel-fuzzer--wasm32-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm-isel-fuzzer--wasm32-O2 Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201804120529:201804130530 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5701986146582528 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40128] New: Trunk doesn't build with libz3-dev of ubuntu 18.04
https://bugs.llvm.org/show_bug.cgi?id=40128
Bug ID: 40128
Summary: Trunk doesn't build with libz3-dev of ubuntu 18.04
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: dcough...@apple.com
Reporter: pmatos@linki.tools
CC: dcough...@apple.com, llvm-bugs@lists.llvm.org
Start a docker machine with ubuntu 18.04.
Install libz3-dev and compile llvm/clang trunk with:
cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=Release
-DCLANG_ANALYZER_ENABLE_Z3_SOLVER=ON -G Ninja ../llvm
You'll get from clang
FAILED:
tools/clang/lib/StaticAnalyzer/Core/CMakeFiles/clangStaticAnalyzerCore.dir/Z3ConstraintManager.cpp.o
/usr/bin/c++ -DGTEST_HAS_RTTI=0 -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
-Itools/clang/lib/StaticAnalyzer/Core
-I/root/llvm/tools/clang/lib/StaticAnalyzer/Core
-I/root/llvm/tools/clang/include -Itools/clang/include -Iinclude
-I/root/llvm/include -fPIC -fvisibility-inlines-hidden -Werror=date-time
-std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual
-Wno-missing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough
-Wno-maybe-uninitialized -Wno-class-memaccess -Wno-noexcept-type
-Wdelete-non-virtual-dtor -Wno-comment -fdiagnostics-color -ffunction-sections
-fdata-sections -fno-common -Woverloaded-virtual -fno-strict-aliasing
-fno-exceptions -fno-rtti -MD -MT
tools/clang/lib/StaticAnalyzer/Core/CMakeFiles/clangStaticAnalyzerCore.dir/Z3ConstraintManager.cpp.o
-MF
tools/clang/lib/StaticAnalyzer/Core/CMakeFiles/clangStaticAnalyzerCore.dir/Z3ConstraintManager.cpp.o.d
-o
tools/clang/lib/StaticAnalyzer/Core/CMakeFiles/clangStaticAnalyzerCore.dir/Z3ConstraintManager.cpp.o
-c /root/llvm/tools/clang/lib/StaticAnalyzer/Core/Z3ConstraintManager.cpp
/root/llvm/tools/clang/lib/StaticAnalyzer/Core/Z3ConstraintManager.cpp: In
function 'void {anonymous}::Z3ErrorHandler(Z3_context, Z3_error_code)':
/root/llvm/tools/clang/lib/StaticAnalyzer/Core/Z3ConstraintManager.cpp:49:57:
error: cannot convert 'Z3_context' {aka '_Z3_context*'} to 'Z3_error_code'
llvm::Twine(Z3_get_error_msg(Context, Error)));
^~~
In file included from /usr/include/z3.h:26,
from
/root/llvm/tools/clang/lib/StaticAnalyzer/Core/Z3ConstraintManager.cpp:23:
/usr/include/z3_api.h:5314:53: note: initializing argument 1 of 'const char*
Z3_get_error_msg(Z3_error_code)'
Z3_string Z3_API Z3_get_error_msg(Z3_error_code err);
~~^~~
My guess is that cmake needs a stricter check for the version of libz3.
--
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 23868] Runtime GP fault when throwing aligned type
https://bugs.llvm.org/show_bug.cgi?id=23868 Eric Fiselier changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Eric Fiselier --- Closing as resolved. Please reopen if you can still reproduce on newel Apple platforms. -- 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 40129] New: [AMDGPU][Regression, bisected] Recent Load/Store optimizer improvements break SI
https://bugs.llvm.org/show_bug.cgi?id=40129 Bug ID: 40129 Summary: [AMDGPU][Regression,bisected] Recent Load/Store optimizer improvements break SI Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: release blocker Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: samuel.pitoi...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Hi, The following commit introduces a bunch of Vulkan CTS failures (~1600) on SI. Tested with RADV. If you want to reproduce the problem, you can run dEQP-VK.clipping.user_defined.clip_cull_distance.vert_tess_geom.1_7 or dEQP-VK.image.image_size.1d.readonly_1 for example. Note that a bunch of vec3 CTS tests fail too, maybe it's an alignment issue that is SI-specific? 4778d2ba9306039e888628874cf5a6c32e6bc004 is the first bad commit commit 4778d2ba9306039e888628874cf5a6c32e6bc004 Author: Neil Henning Date: Wed Dec 12 16:15:21 2018 + [AMDGPU] Extend the SI Load/Store optimizer to combine more things. I've extended the load/store optimizer to be able to produce dwordx3 loads and stores, This change allows many more load/stores to be combined, and results in much more optimal code for our hardware. Differential Revision: https://reviews.llvm.org/D54042 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@348937 91177308-0d34-0410-b5e6-96231b3b80d8 -- 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 40050] TestCompDirSymLink.py fails on Linux
https://bugs.llvm.org/show_bug.cgi?id=40050 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||lab...@google.com --- Comment #1 from lab...@google.com --- This should be fixed by r349819 -- 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 40049] TestNamespace.py fails on Linux
https://bugs.llvm.org/show_bug.cgi?id=40049 lab...@google.com changed: What|Removed |Added Status|NEW |RESOLVED CC||lab...@google.com Resolution|--- |FIXED --- Comment #1 from lab...@google.com --- This should be fixed by r349528. -- 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 40048] TestCppNsImport.py fails on Linux
https://bugs.llvm.org/show_bug.cgi?id=40048 Gábor Márton changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #2 from Gábor Márton --- Yes, it has been fixed, confirmed. *** This bug has been marked as a duplicate of bug 40049 *** -- 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 12003 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Comment #1 on issue 12003 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12003#c1 ClusterFuzz has detected this issue as fixed in range 201812200235:201812210355. Detailed report: https://oss-fuzz.com/testcase?key=5708612274487296 Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffdd509cd48 Crash State: clang::DiagnosticIDs::isUnrecoverable clang::DiagnosticIDs::ProcessDiag clang::DiagnosticsEngine::EmitCurrentDiagnostic Sanitizer: address (ASAN) Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812200235:201812210355 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5708612274487296 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11929 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in ConvertDeclSpecToType
Comment #1 on issue 11929 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in ConvertDeclSpecToType https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11929#c1 ClusterFuzz has detected this issue as fixed in range 201812200235:201812210355. Detailed report: https://oss-fuzz.com/testcase?key=5646780918661120 Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff9d25bfb8 Crash State: ConvertDeclSpecToType GetDeclSpecTypeForDeclarator clang::Sema::GetTypeForDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201807230239:201807240240 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812200235:201812210355 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5646780918661120 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11904 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead
Comment #1 on issue 11904 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11904#c1 ClusterFuzz has detected this issue as fixed in range 201812200235:201812210355. Detailed report: https://oss-fuzz.com/testcase?key=5699682097954816 Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffde0e4ded8 Crash State: clang::Preprocessor::PeekAhead clang::Parser::isCXX11AttributeSpecifier clang::Parser::ParseDeclarationSpecifiers Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812160234:201812170233 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812200235:201812210355 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5699682097954816 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11835 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in processTypeAttrs
Comment #1 on issue 11835 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in processTypeAttrs https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11835#c1 ClusterFuzz has detected this issue as fixed in range 201812200235:201812210355. Detailed report: https://oss-fuzz.com/testcase?key=5720705191116800 Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffd1a85cfe0 Crash State: processTypeAttrs ConvertDeclSpecToType GetDeclSpecTypeForDeclarator Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201808300127:201808310127 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812200235:201812210355 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5720705191116800 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11875 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::ConvertUTF8toWide
Comment #1 on issue 11875 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::ConvertUTF8toWide https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11875#c1 ClusterFuzz has detected this issue as fixed in range 201812200235:201812210355. Detailed report: https://oss-fuzz.com/testcase?key=5686258110562304 Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe70079c98 Crash State: llvm::ConvertUTF8toWide clang::StringLiteralParser::CopyStringFragment clang::StringLiteralParser::init Sanitizer: address (ASAN) Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812200235:201812210355 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5686258110562304 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11929 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in ConvertDeclSpecToType
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 11929 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in ConvertDeclSpecToType https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11929#c2 ClusterFuzz testcase 5646780918661120 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] Issue 11817 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Comment #1 on issue 11817 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11817#c1 ClusterFuzz has detected this issue as fixed in range 201812200235:201812210355. Detailed report: https://oss-fuzz.com/testcase?key=5746648571969536 Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffc17cc09c8 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=201808310127:201809010125 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201812200235:201812210355 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5746648571969536 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 11875 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::ConvertUTF8toWide
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 11875 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::ConvertUTF8toWide https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11875#c2 ClusterFuzz testcase 5686258110562304 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] Issue 11904 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 11904 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11904#c2 ClusterFuzz testcase 5699682097954816 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] Issue 12003 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 12003 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12003#c2 ClusterFuzz testcase 5708612274487296 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] Issue 11835 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in processTypeAttrs
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 11835 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in processTypeAttrs https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11835#c2 ClusterFuzz testcase 5720705191116800 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] Issue 11817 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 11817 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11817#c2 ClusterFuzz testcase 5746648571969536 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 40130] New: [AMDGPU] Monster Hunter World renders incorrectly when SILoadStoreOptimizer is enabled
https://bugs.llvm.org/show_bug.cgi?id=40130 Bug ID: 40130 Summary: [AMDGPU] Monster Hunter World renders incorrectly when SILoadStoreOptimizer is enabled Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: release blocker Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: samuel.pitoi...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 21262 --> https://bugs.llvm.org/attachment.cgi?id=21262&action=edit LLVM IR Hi, Disabling SILoadStoreOptimizer for the attached IR fixes the problem. The IR right after that pass looks correct to me. This probably trigger a problem later in the process. Note that LLVM 6 doesn't expose the issue. [1] https://github.com/doitsujin/dxvk/issues/701 -- 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 40131] New: ompt/misc/control_tool.c failing on AArch64
https://bugs.llvm.org/show_bug.cgi?id=40131
Bug ID: 40131
Summary: ompt/misc/control_tool.c failing on AArch64
Product: OpenMP
Version: unspecified
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Runtime Library
Assignee: unassignedb...@nondot.org
Reporter: gree...@obbligato.org
CC: hah...@hahnjo.de, llvm-bugs@lists.llvm.org
I am seeing the following running the OMPT tests on AArch64:
/ptmp/dag/cce-clang/openmp/runtime/test/ompt/misc/control_tool.c:26:17: error:
CHECK-NEXT: expected string not found in input
// CHECK-NEXT: {{^}}[[MASTER_ID]]: current_address={{.*}}[[RETURN_ADDRESS]]
^
:9:1: note: scanning from here
281474976710657: current_address=0x403594 or 0x403590
^
:9:1: note: with variable "MASTER_ID" equal to "281474976710657"
281474976710657: current_address=0x403594 or 0x403590
^
:9:1: note: with variable "RETURN_ADDRESS" equal to "0x40358c"
281474976710657: current_address=0x403594 or 0x403590
^
:9:13: note: possible intended match here
281474976710657: current_address=0x403594 or 0x403590
Originally, other OMPT tests will failing in the same way. Removing
-fno-experimental-isel from the OMP testing flags caused those tests to start
passing.
--
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 39981] Regression: TypeLoc.getTypePtr() crashes while parsing a certain piece of C++ code
https://bugs.llvm.org/show_bug.cgi?id=39981 Dimitar Dobrev changed: What|Removed |Added Resolution|--- |INVALID Status|CONFIRMED |RESOLVED --- Comment #10 from Dimitar Dobrev --- This turns out to be a problem in our code, it needed to be updated to match the new behaviour. We now use getCanonicalTypeInternal instead of desugar. -- 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 40132] New: Categories in blacklist do not work
https://bugs.llvm.org/show_bug.cgi?id=40132 Bug ID: 40132 Summary: Categories in blacklist do not work Product: compiler-rt Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: ubsan Assignee: unassignedb...@nondot.org Reporter: antosh...@gmail.com CC: llvm-bugs@lists.llvm.org We've attemted to manually run the misaligned test from test/ubsan/TestCases/TypeCheck/misaligned.cpp with the following compiler options `-fsanitize=undefined -fsanitize-blacklist=file.txt -O0 -g`. Content of the file.txt is the following src:*=alignment The suppression did not work. Replacing =alignment with =undefined did not help. Only removing the =alignment helped, which is not nice because we wished to suppress only a single category of errors. -- 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 40133] New: type lookup doesn't work with nested types when using Native PDB reader.
https://bugs.llvm.org/show_bug.cgi?id=40133
Bug ID: 40133
Summary: type lookup doesn't work with nested types when using
Native PDB reader.
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: lldb-...@lists.llvm.org
Reporter: ztur...@google.com
CC: aleksandr.ura...@jetbrains.com,
llvm-bugs@lists.llvm.org, mose...@google.com
struct S {
struct NestedStruct {};
};
(lldb) type lookup -- S::NestedStruct
will fail to return any types.
The reason for this is that LLDB parses this and attempts to look up just the
type "NestedStruct". It expects us to return a list of all types named
NestedStruct, including those which are nested in other structs. Then, it will
filter this list itself.
Our Native PDB reader already pre-processes the TPI stream when the PDB is
loaded and discovers all nested types, so we have the ability to index nested
types by their basename at no incremental complexity, and this should make it
possible for this to work.
--
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 37502] _mm_set_ps is lowered badly with sse4
https://bugs.llvm.org/show_bug.cgi?id=37502 Sanjay Patel changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)||r349937 --- Comment #3 from Sanjay Patel --- Should be fixed with: https://reviews.llvm.org/rL349937 -- 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 38373] [lldbsuite] Several tests are flakey on windows and will fail every several dozen runs
https://bugs.llvm.org/show_bug.cgi?id=38373 Stella Stamenova changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #3 from Stella Stamenova --- These tests are still flakey. They have been disabled to allow the windows bot to be green. TestMultipleBreakpoints.py TestThreadExit.py TestNamespaceLookup.py TestNumThreads.py TestMemoryCache.py TestExitDuringStep.py -- 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 35023] [arm] Assertion failed: (LiveCPSR && "CPSR liveness tracking is wrong!"), function UpdateCPSRUse, file lib/Target/ARM/Thumb2SizeReduction.cpp, line 961
https://bugs.llvm.org/show_bug.cgi?id=35023 Florian Hahn changed: 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38186] llvm-objdump doesn't handle symbols referring the .plt section, or print symbols within it.
https://bugs.llvm.org/show_bug.cgi?id=38186 saugust...@google.com changed: What|Removed |Added Resolution|--- |FIXED 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 38668] Regression introduced by r326520
https://bugs.llvm.org/show_bug.cgi?id=38668 Artem Dergachev changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #4 from Artem Dergachev --- Reverted and still struggling a bit. -- 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 36381] Crash in NonNullParamChecker / clang::ento::RangedConstraintManager::assumeSymUnsupported()
https://bugs.llvm.org/show_bug.cgi?id=36381 Bug 36381 depends on bug 38668, which changed state. Bug 38668 Summary: Regression introduced by r326520 https://bugs.llvm.org/show_bug.cgi?id=38668 What|Removed |Added Status|RESOLVED|REOPENED 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40134] New: __executable_start doesn't get added to executables
https://bugs.llvm.org/show_bug.cgi?id=40134
Bug ID: 40134
Summary: __executable_start doesn't get added to executables
Product: lld
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: ELF
Assignee: unassignedb...@nondot.org
Reporter: thomasander...@google.com
CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org
__executable_start (and other symbols like __ehdr_start) do not get added by
lld unless -shared is used.
$ cat main.c
#include
extern char __executable_start;
int main(void) {
printf("%p\n", &__executable_start);
return 0;
}
$ clang main.c -c -o main.o -fpic
$ clang main.o -o main -fuse-ld=bfd
$ clang main.o -o main -fuse-ld=gold
$ clang main.o -o main.so -fuse-ld=lld -shared
$ clang main.o -o main -fuse-ld=lld
/usr/bin/ld.lld: error: main.c:(function main): undefined symbol
'__executable_start'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
--
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 40135] New: [x86] keep math/logic on vector unit to avoid insert/extract
https://bugs.llvm.org/show_bug.cgi?id=40135
Bug ID: 40135
Summary: [x86] keep math/logic on vector unit to avoid
insert/extract
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: spatel+l...@rotateright.com
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, spatel+l...@rotateright.com
We have a potential regression with shift lowering via rotates while trying to
do scalarization in:
https://reviews.llvm.org/D55722
I don't think we're allowed to do anything with this in IR even if the pattern
was appearing there:
define <4 x i32> @shiftamount_math(<4 x i32> %x, <4 x i32> %y) {
%e = extractelement <4 x i32> %x, i32 0
%s = sub i32 32, %e
%i = insertelement <4 x i32> undef, i32 %s, i32 0
%splat = shufflevector <4 x i32> %i, <4 x i32> undef, <4 x i32>
zeroinitializer
%shift = shl <4 x i32> %y, %splat
ret <4 x i32> %shift
}
$ llc -o - vecshift.ll
...
movd%xmm0, %eax
movl$32, %ecx
subl%eax, %ecx
movd%ecx, %xmm0
pslld %xmm0, %xmm1
movdqa %xmm1, %xmm0
retq
We would probably be better off loading the '32' as a splat constant and doing
the 'sub' as a vector op:
movdqa LCPI1_0(%rip), %xmm2## xmm2 = [32,32,32,32]
psubd %xmm0, %xmm2
pxor%xmm0, %xmm0
movss %xmm2, %xmm0## xmm0 = xmm2[0],xmm0[1,2,3]
pslld %xmm0, %xmm1
movdqa %xmm1, %xmm0
It's ugly because of the x86
vector-shift-by-variable-but-not-really-a-vector-shift instruction that takes a
64-bit shift amount, but that beats transferring to scalar and back?
--
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 40060] [X86] optimizeCompareInstr can use the S flag from the BEXTR instruction which is undefined
https://bugs.llvm.org/show_bug.cgi?id=40060 Craig Topper changed: What|Removed |Added Fixed By Commit(s)||r349956 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Craig Topper --- Fixed in r349956 -- 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 34920] __builtin_mul_overflow unsupported for mixed-sign 64-bit operands on 32-bit architectures
https://bugs.llvm.org/show_bug.cgi?id=34920 Vedant Kumar changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||r349542 --- Comment #17 from Vedant Kumar --- I'll mark this as resolved by r349542. -- 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 40118] Miscompilation of C++ constructors
https://bugs.llvm.org/show_bug.cgi?id=40118 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Fixed By Commit(s)||r349945 --- Comment #7 from Reid Kleckner --- That patch became r349945. Thanks for reducing that V8 ASan bug. The fix will probably get to chromium in a few weeks. -- 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 40136] New: Compiler should issue an error or warning when adding a checker that does not include a URI
https://bugs.llvm.org/show_bug.cgi?id=40136
Bug ID: 40136
Summary: Compiler should issue an error or warning when adding
a checker that does not include a URI
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: douglas_y...@playstation.sony.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
Upstream change r349812 addded a 2-bit Documentation field to checkers that
caused an unhelpful failure ("Invalid bits") to be hit during our internal
build during tablegen because our out-of-tree checkers did not have this field.
After tracking down the cause of the error, I think it would be more helpful if
the compiler or tablegen issued an error saying the field was missing so that
out-of-tree checkers can be quickly/easily 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12128 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-guard_widening: ASSERT: Index < Length && "Invalid index!"
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-2018-12-22 Type: Bug New issue 12128 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-guard_widening: ASSERT: Index < Length && "Invalid index!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12128 Detailed report: https://oss-fuzz.com/testcase?key=5652880376201216 Project: llvm Fuzzer: libFuzzer_llvm-opt-fuzzer--x86_64-guard_widening Fuzz target binary: llvm-opt-fuzzer--x86_64-guard_widening Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Index < Length && "Invalid index!" BitcodeReader::parseModule llvm::BitcodeModule::getModuleImpl Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802190622:201802200626 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5652880376201216 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
