[llvm-bugs] Issue 3835 in oss-fuzz: llvm/clangd-fuzzer: Abrt in std::__1::__vector_base_common::__throw_length_error
Comment #2 on issue 3835 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: Abrt in std::__1::__vector_base_common::__throw_length_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3835#c2 ClusterFuzz has detected this issue as fixed in range 201710270453:201710280456. Detailed report: https://oss-fuzz.com/testcase?key=5091865293488128 Project: llvm Fuzzer: libFuzzer_llvm_clangd-fuzzer Fuzz target binary: clangd-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: std::__1::__vector_base_common::__throw_length_error std::__1::vector >::vector clang::clangd::runLanguageServerLoop Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710260448:201710270453 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710270453:201710280456 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5091865293488128 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 3836 in oss-fuzz: llvm/clangd-fuzzer: Out-of-memory in llvm_clangd-fuzzer
Comment #2 on issue 3836 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: Out-of-memory in llvm_clangd-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3836#c2 ClusterFuzz has detected this issue as fixed in range 201710270453:201710280456. Detailed report: https://oss-fuzz.com/testcase?key=5216842936221696 Project: llvm Fuzzer: libFuzzer_llvm_clangd-fuzzer Fuzz target binary: clangd-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm_clangd-fuzzer Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710260448:201710270453 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710270453:201710280456 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5216842936221696 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 3727 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Global-buffer-overflow in p_bracket
Comment #5 on issue 3727 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/llvm-special-case-list-fuzzer: Global-buffer-overflow in p_bracket https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3727#c5 ClusterFuzz has detected this issue as fixed in range 201710270453:201710280456. Detailed report: https://oss-fuzz.com/testcase?key=5367749363630080 Project: llvm Fuzzer: libFuzzer_llvm_llvm-special-case-list-fuzzer Fuzz target binary: llvm-special-case-list-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Global-buffer-overflow READ 1 Crash Address: 0x006a18bc Crash State: p_bracket p_ere p_ere Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710270453:201710280456 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5367749363630080 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 3798 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Global-buffer-overflow in p_b_symbol
Comment #2 on issue 3798 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/llvm-special-case-list-fuzzer: Global-buffer-overflow in p_b_symbol https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3798#c2 ClusterFuzz has detected this issue as fixed in range 201710270453:201710280456. Detailed report: https://oss-fuzz.com/testcase?key=6124359660863488 Project: llvm Fuzzer: libFuzzer_llvm_llvm-special-case-list-fuzzer Fuzz target binary: llvm-special-case-list-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Global-buffer-overflow READ 1 Crash Address: 0x006a22a3 Crash State: p_b_symbol p_bracket p_ere Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710270453:201710280456 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6124359660863488 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 3841 in oss-fuzz: llvm/clangd-fuzzer: ASSERT: Val && "isa<> used on a null pointer"
Comment #2 on issue 3841 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: ASSERT: Val && "isa<> used on a null pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3841#c2 ClusterFuzz has detected this issue as fixed in range 201710270453:201710280456. Detailed report: https://oss-fuzz.com/testcase?key=6197943120953344 Project: llvm Fuzzer: libFuzzer_llvm_clangd-fuzzer Fuzz target binary: clangd-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Val && "isa<> used on a null pointer" clang::clangd::JSONRPCDispatcher::call clang::clangd::runLanguageServerLoop Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710260448:201710270453 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710270453:201710280456 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6197943120953344 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 3798 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Global-buffer-overflow in p_b_symbol
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 3798 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/llvm-special-case-list-fuzzer: Global-buffer-overflow in p_b_symbol https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3798#c3 ClusterFuzz testcase 6124359660863488 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 3841 in oss-fuzz: llvm/clangd-fuzzer: ASSERT: Val && "isa<> used on a null pointer"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 3841 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: ASSERT: Val && "isa<> used on a null pointer" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3841#c3 ClusterFuzz testcase 6197943120953344 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 3835 in oss-fuzz: llvm/clangd-fuzzer: Abrt in std::__1::__vector_base_common::__throw_length_error
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 3835 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: Abrt in std::__1::__vector_base_common::__throw_length_error https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3835#c3 ClusterFuzz testcase 5091865293488128 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 3836 in oss-fuzz: llvm/clangd-fuzzer: Out-of-memory in llvm_clangd-fuzzer
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 3836 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: Out-of-memory in llvm_clangd-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3836#c3 ClusterFuzz testcase 5216842936221696 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 3727 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Global-buffer-overflow in p_bracket
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 3727 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/llvm-special-case-list-fuzzer: Global-buffer-overflow in p_bracket https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3727#c6 ClusterFuzz testcase 5367749363630080 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 3867 in oss-fuzz: llvm/clangd-fuzzer: Use-after-poison in llvm::yaml::Scanner::scanValue
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-10-28 New issue 3867 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: Use-after-poison in llvm::yaml::Scanner::scanValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3867 Detailed report: https://oss-fuzz.com/testcase?key=4553604959567872 Project: llvm Fuzzer: libFuzzer_llvm_clangd-fuzzer Fuzz target binary: clangd-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Use-after-poison READ 8 Crash Address: 0x621029f0 Crash State: llvm::yaml::Scanner::scanValue llvm::yaml::Scanner::fetchMoreTokens llvm::yaml::Scanner::peekNext Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710260448:201710270453 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4553604959567872 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 35115] New: clang-cl: error: expected identifier 'short' with inline asm jne short foo
https://bugs.llvm.org/show_bug.cgi?id=35115
Bug ID: 35115
Summary: clang-cl: error: expected identifier 'short' with
inline asm jne short foo
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: amine.kha...@reactos.org
CC: llvm-bugs@lists.llvm.org
int main() {
__asm {
jne short foo
foo:
push ebx
}
}
cl compiles it, but clang-cl emits:
test.c(3,13) : error: expected identifier
jne short foo
^
test.c(3,13) : error: use of undeclared label 'short foo
foo:
push ebx'
2 errors 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35116] New: clang-cl: missing #pragma function support leads to error: definition of builtin function
https://bugs.llvm.org/show_bug.cgi?id=35116
Bug ID: 35116
Summary: clang-cl: missing #pragma function support leads to
error: definition of builtin function
Product: clang
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: amine.kha...@reactos.org
CC: llvm-bugs@lists.llvm.org
unsigned int _rotr(unsigned int value, int shift);
#pragma intrinsic(_rotr)
#pragma function(_rotr)
unsigned int _rotr(unsigned int value, int shift) { return 0;}
int main() {}
cl compiles it but clang-cl emits:
test.c(5,14) : error: definition of builtin function '_rotr'
unsigned int _rotr(unsigned int value, int shift) { return 0;}
^
1 error 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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34492] [meta] 5.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=34492 Bug 34492 depends on bug 34880, which changed state. Bug 34880 Summary: [ConstantFold] llvm crashes when folding a GEP with vector index https://bugs.llvm.org/show_bug.cgi?id=34880 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 34880] [ConstantFold] llvm crashes when folding a GEP with vector index
https://bugs.llvm.org/show_bug.cgi?id=34880 Haicheng Wu changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Haicheng Wu --- Fixed in r316824. -- 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 35117] New: Merge r316824 into 5.0.1
https://bugs.llvm.org/show_bug.cgi?id=35117 Bug ID: 35117 Summary: Merge r316824 into 5.0.1 Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: release blocker Priority: P Component: Core LLVM classes Assignee: unassignedb...@nondot.org Reporter: haich...@codeaurora.org CC: llvm-bugs@lists.llvm.org https://reviews.llvm.org/rL316824 [ConstantFold] Fix a crash when folding a GEP that has vector index LLVM crashes when factoring out an out-of-bound index into preceding dimension and the preceding dimension uses vector index. Simply bail out now when this case happens. -- 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 34857] 8 bytes trivially copy constructible and destructible structure passed par memory instead of register
https://bugs.llvm.org/show_bug.cgi?id=34857 Richard Smith changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #10 from Richard Smith --- GCC trunk also implements the corrected ABI rule (https://godbolt.org/g/YkNau8). -- 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 3875 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ((OffsetImm & 1) == 0) && "Unexpected offset to merge"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-10-28 New issue 3875 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/llvm-isel-fuzzer--aarch64-O2: ASSERT: ((OffsetImm & 1) == 0) && "Unexpected offset to merge" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3875 Detailed report: https://oss-fuzz.com/testcase?key=6156644393156608 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-O2 Fuzz target binary: llvm-isel-fuzzer--aarch64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: ((OffsetImm & 1) == 0) && "Unexpected offset to merge" AArch64LoadStoreOpt::optimizeBlock AArch64LoadStoreOpt::runOnMachineFunction Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6156644393156608 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] Issue 3878 in oss-fuzz: llvm/clangd-fuzzer: Null-dereference READ in void llvm::yaml::skip
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-10-29 New issue 3878 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: Null-dereference READ in void llvm::yaml::skip https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3878 Detailed report: https://oss-fuzz.com/testcase?key=4676556451479552 Project: llvm Fuzzer: libFuzzer_llvm_clangd-fuzzer Fuzz target binary: clangd-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: void llvm::yaml::skip llvm::yaml::MappingNode::increment clang::clangd::JSONRPCDispatcher::call Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710260448:201710270453 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4676556451479552 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 35118] New: clang crashes on x86_64-linux-gnu with Assertion `Us < (1u << NumUserOperandsBits) && "Too many operands"' failed.
https://bugs.llvm.org/show_bug.cgi?id=35118 Bug ID: 35118 Summary: clang crashes on x86_64-linux-gnu with Assertion `Us < (1u << NumUserOperandsBits) && "Too many operands"' failed. Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: helloqi...@gmail.com CC: llvm-bugs@lists.llvm.org $ clang-trunk -v clang version 6.0.0 (trunk 316829) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: /usr/local/bin $ clang-trunk -c abc.c clang-6.0: /home/absozero/trunk/llvm/lib/IR/User.cpp:116: static void* llvm::User::allocateFixedOperandUser(size_t, unsigned int, unsigned int): Assertion `Us < (1u << NumUserOperandsBits) && "Too many operands"' failed. #0 0x020c308a llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x20c308a) #1 0x020c0f2e llvm::sys::RunSignalHandlers() (/home/absozero/trunk/root-clang/bin/clang-6.0+0x20c0f2e) #2 0x020c1082 SignalHandler(int) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x20c1082) #3 0x7fd5c5b7c330 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x10330) #4 0x7fd5c46f9c37 gsignal /build/eglibc-oGUzwX/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56:0 #5 0x7fd5c46fd028 abort /build/eglibc-oGUzwX/eglibc-2.19/stdlib/abort.c:91:0 #6 0x7fd5c46f2bf6 __assert_fail_base /build/eglibc-oGUzwX/eglibc-2.19/assert/assert.c:92:0 #7 0x7fd5c46f2ca2 (/lib/x86_64-linux-gnu/libc.so.6+0x2fca2) #8 0x01c2f806 (/home/absozero/trunk/root-clang/bin/clang-6.0+0x1c2f806) #9 0x01b6048a llvm::ConstantUniqueMap::getOrCreate(llvm::ArrayType*, llvm::ConstantAggrKeyType) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x1b6048a) #10 0x01b6068b llvm::ConstantArray::get(llvm::ArrayType*, llvm::ArrayRef) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x1b6068b) #11 0x02299cbb clang::StmtVisitorBase::Visit(clang::Stmt*, clang::QualType) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x2299cbb) #12 0x02297b93 clang::CodeGen::ConstantEmitter::tryEmitPrivate(clang::Expr const*, clang::QualType) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x2297b93) #13 0x02297d76 clang::CodeGen::ConstantEmitter::tryEmitPrivateForMemory(clang::Expr const*, clang::QualType) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x2297d76) #14 0x022998e1 clang::StmtVisitorBase::Visit(clang::Stmt*, clang::QualType) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22998e1) #15 0x02299f09 clang::CodeGen::ConstantEmitter::tryEmitPrivateForVarInit(clang::VarDecl const&) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x2299f09) #16 0x0229a012 clang::CodeGen::ConstantEmitter::tryEmitAbstractForInitializer(clang::VarDecl const&) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x229a012) #17 0x023fec78 clang::CodeGen::CodeGenFunction::EmitAutoVarInit(clang::CodeGen::CodeGenFunction::AutoVarEmission const&) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x23fec78) #18 0x02402932 clang::CodeGen::CodeGenFunction::EmitAutoVarDecl(clang::VarDecl const&) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x2402932) #19 0x02402a16 clang::CodeGen::CodeGenFunction::EmitVarDecl(clang::VarDecl const&) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x2402a16) #20 0x02402d94 clang::CodeGen::CodeGenFunction::EmitDecl(clang::Decl const&) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x2402d94) #21 0x022a716f clang::CodeGen::CodeGenFunction::EmitDeclStmt(clang::DeclStmt const&) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22a716f) #22 0x022b4362 clang::CodeGen::CodeGenFunction::EmitSimpleStmt(clang::Stmt const*) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22b4362) #23 0x022b0130 clang::CodeGen::CodeGenFunction::EmitStmt(clang::Stmt const*, llvm::ArrayRef) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22b0130) #24 0x022b12db clang::CodeGen::CodeGenFunction::EmitCompoundStmtWithoutScope(clang::CompoundStmt const&, bool, clang::CodeGen::AggValueSlot) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22b12db) #25 0x022b15b4 clang::CodeGen::CodeGenFunction::EmitCompoundStmt(clang::CompoundStmt const&, bool, clang::CodeGen::AggValueSlot) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22b15b4) #26 0x022b43c3 clang::CodeGen::CodeGenFunction::EmitSimpleStmt(clang::Stmt const*) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22b43c3) #27 0x022b0130 clang::CodeGen::CodeGenFunction::EmitStmt(clang::Stmt const*, llvm::ArrayRef) (/home/absozero/trunk/root-clang/bin/clang-6.0+0x22b0130) #28 0x022b12db clang::CodeGen::CodeGenFunction::EmitCompoundStmtWithoutScope(clang::CompoundStmt const&,
[llvm-bugs] [Bug 35068] Possible bad optimisation of unsigned atomic fetch_sub(1) > 1 on x64
https://bugs.llvm.org/show_bug.cgi?id=35068 Craig Topper changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Craig Topper --- Should be fixed with r316860. -- 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 3890 in oss-fuzz: llvm/clangd-fuzzer: Null-dereference READ in void llvm::yaml::skip
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, llvm-b...@lists.llvm.org, v...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2017-10-29 New issue 3890 by monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm/clangd-fuzzer: Null-dereference READ in void llvm::yaml::skip https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3890 Detailed report: https://oss-fuzz.com/testcase?key=5861264459825152 Project: llvm Fuzzer: libFuzzer_llvm_clangd-fuzzer Fuzz target binary: clangd-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: void llvm::yaml::skip llvm::yaml::SequenceNode::skip llvm::yaml::SequenceNode::skip Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710260448:201710270453 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5861264459825152 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
