[llvm-bugs] Issue 33869 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Parser::ParseRHSOfBinaryExpression
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-05-01 Type: Bug New issue 33869 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Parser::ParseRHSOfBinaryExpression https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33869 Detailed Report: https://oss-fuzz.com/testcase?key=4969432733581312 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe3e16a9c0 Crash State: clang::Parser::ParseRHSOfBinaryExpression Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202006290157:202006300157 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4969432733581312 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] [Bug 50191] New: clang crashes at -O2 in llvm/lib/Analysis/ValueTracking.cpp:2603: llvm::Optional getInvertibleOperand(const llvm::Operator*, const llvm::Operator*): Assertio
https://bugs.llvm.org/show_bug.cgi?id=50191
Bug ID: 50191
Summary: clang crashes at -O2 in
llvm/lib/Analysis/ValueTracking.cpp:2603:
llvm::Optional
getInvertibleOperand(const llvm::Operator*, const
llvm::Operator*): Assertion `BO1->getOperand(*Idx) ==
PN1 && BO2->getOperand(*Idx) == PN2' failed
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: haoxi...@gmail.com
CC: llvm-bugs@lists.llvm.org
Hi all.
$cat small.c
#include
int i_2, c_3;
void fn1() {
uint8_t uc_7;
int32_t i_9;
uint64_t uli_10;
for (; uc_7; uc_7++)
for (; c_3; c_3++) {
uint16_t us_16 = 0;
for (; us_16 <= 42; us_16++)
i_9 *= uli_10 | ((i_2 -= i_9) ?: (uc_7 = 3));
}
}
$clang -w -O2 small.c
clang-13:
/home/haoxin/haoxin-data/dut-research/compilers/llvm-project/llvm/lib/Analysis/ValueTracking.cpp:2603:
llvm::Optional getInvertibleOperand(const llvm::Operator*, const
llvm::Operator*): Assertion `BO1->getOperand(*Idx) == PN1 &&
BO2->getOperand(*Idx) == PN2' failed.
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace, preprocessed source, and associated run script.
Stack dump:
0. Program arguments:
/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13
-cc1 -triple x86_64-unknown-linux-gnu -emit-obj --mrelax-relocations
-disable-free -main-file-name small.c -mrelocation-model static
-mframe-pointer=none -fmath-errno -fno-rounding-math -mconstructor-aliases
-munwind-tables -target-cpu x86-64 -tune-cpu generic -debugger-tuning=gdb
-fcoverage-compilation-dir=/home/haoxin/haoxin-data/test -resource-dir
/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/lib/clang/13.0.0
-c-isystem /usr/local/include/csmith-2.3.0 -cxx-isystem
/usr/local/include/csmith-2.3.0 -internal-isystem
/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/lib/clang/13.0.0/include
-internal-isystem /usr/local/include -internal-isystem
/usr/lib/gcc/x86_64-linux-gnu/10/../../../../x86_64-linux-gnu/include
-internal-externc-isystem /usr/include/x86_64-linux-gnu
-internal-externc-isystem /include -internal-externc-isystem /usr/include -O2
-w -fdebug-compilation-dir=/home/haoxin/haoxin-data/test -ferror-limit 19
-fgnuc-version=4.2.1 -fcolor-diagnostics -vectorize-loops -vectorize-slp
-faddrsig -D__GCC_HAVE_DWARF2_CFI_ASM=1 -o /tmp/small-8b700f.o -x c small.c
1. parser at end of file
2. Optimizer
#0 0x55fbe6cfb37c llvm::sys::PrintStackTrace(llvm::raw_ostream&, int)
(/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13+0x35b537c)
#1 0x55fbe6cf9184 llvm::sys::RunSignalHandlers()
(/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13+0x35b3184)
#2 0x55fbe6cf92f3 SignalHandler(int)
(/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13+0x35b32f3)
#3 0x7ff27a7a7980 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x12980)
#4 0x7ff2793cffb7 gsignal
/build/glibc-S9d2JN/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:51:0
#5 0x7ff2793d1921 abort /build/glibc-S9d2JN/glibc-2.27/stdlib/abort.c:81:0
#6 0x7ff2793c148a __assert_fail_base
/build/glibc-S9d2JN/glibc-2.27/assert/assert.c:89:0
#7 0x7ff2793c1502 (/lib/x86_64-linux-gnu/libc.so.6+0x30502)
#8 0x55fbe5e97f0a getInvertibleOperand(llvm::Operator const*,
llvm::Operator const*)
(/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13+0x2751f0a)
#9 0x55fbe5eb13a3 isKnownNonEqual(llvm::Value const*, llvm::Value const*,
unsigned int, (anonymous namespace)::Query const&) [clone .part.1207]
(/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13+0x276b3a3)
#10 0x55fbe5eb19d2 llvm::isKnownNonEqual(llvm::Value const*, llvm::Value
const*, llvm::DataLayout const&, llvm::AssumptionCache*, llvm::Instruction
const*, llvm::DominatorTree const*, bool)
(/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13+0x276b9d2)
#11 0x55fbe5d1a8bf SimplifyICmpInst(unsigned int, llvm::Value*,
llvm::Value*, llvm::SimplifyQuery const&, unsigned int)
(/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13+0x25d48bf)
#12 0x55fbe677c8f5 llvm::InstCombinerImpl::visitICmpInst(llvm::ICmpInst&)
(/media/haoxin/SeagateData/haoxin-data/dut-research/compilers/llvm-project/build-20210427/bin/clang-13+0x30368f5)
#13 0x55fb
[llvm-bugs] [Bug 50192] New: Frontend crash when decomposing array
https://bugs.llvm.org/show_bug.cgi?id=50192
Bug ID: 50192
Summary: Frontend crash when decomposing array
Product: clang
Version: 11.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++17
Assignee: unassignedclangb...@nondot.org
Reporter: koncek.mar...@gmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
clang compiler crashes on the following:
https://godbolt.org/z/ecarnE7no
```
template
struct S
{
void f()
{
for (auto [news, olds] : (int[2][2]){{1,2}, {3,4}})
{
news = olds;
}
}
};
int main()
{
S s;
s.f();
}
```
--
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 33870 in oss-fuzz: llvm:llvm-isel-fuzzer--aarch64-gisel: Heap-use-after-free in llvm::MetadataTracking::untrack
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2021-05-01 Type: Bug-Security New issue 33870 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--aarch64-gisel: Heap-use-after-free in llvm::MetadataTracking::untrack https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33870 Detailed Report: https://oss-fuzz.com/testcase?key=5625425813438464 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-isel-fuzzer--aarch64-gisel Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Heap-use-after-free READ 1 Crash Address: 0x60a22368 Crash State: llvm::MetadataTracking::untrack llvm::MachineIRBuilder::setMF AArch64InstructionSelector::setupMF Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202104300622:202105010606 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5625425813438464 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 33856 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 33856 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33856#c1 ClusterFuzz testcase 6443933795221504 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202104300622:202105010606 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 33858 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::lookup
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 33858 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DeclContext::lookup https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33858#c1 ClusterFuzz testcase 6709977558417408 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202104300622:202105010606 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 33864 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Sema::LookupName
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 33864 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Sema::LookupName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33864#c1 ClusterFuzz testcase 4524446472863744 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202104300622:202105010606 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 32350 in oss-fuzz: llvm:clang-objc-fuzzer: Stack-overflow in llvm::FoldingSetNodeID::operator==
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #1 on issue 32350 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Stack-overflow in llvm::FoldingSetNodeID::operator== https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=32350#c1 ClusterFuzz testcase 4735402880663552 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202104300622:202105010606 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 27686 in oss-fuzz: llvm: Fuzzing build failure
Comment #27 on issue 27686 by ClusterFuzz-External: llvm: Fuzzing build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27686#c27 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-aee5d063-5bc9-4e21-8ae9-6d4382819ff3.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] [Bug 50193] New: M1 | 20F5046g | 11.4 | LLDB Stack Dump | memory read --outfile
https://bugs.llvm.org/show_bug.cgi?id=50193 Bug ID: 50193 Summary: M1 | 20F5046g | 11.4 | LLDB Stack Dump | memory read --outfile Product: lldb Version: 11.0 Hardware: Macintosh OS: MacOS X Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: h02...@gmail.com CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org Hello & Good Day- The stdout says.. PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace. Sorry if this has already been Reported or is judged to be Noise. Minimized Reproduction Case lldb-1205.0.22 Apple Swift version 5.4 (swiftlang-1205.0.26.4 clang-1205.0.19.54) sysctl -a | grep version user.posix2_version: 200112 kern.version: Darwin Kernel Version 20.5.0: Thu Apr 15 05:31:18 PDT 2021; root:xnu-7195.120.38.111.1~4/RELEASE_ARM64_T8101 kern.posix1version: 200112 kern.osversion: 20F5046g kern.iossupportversion: 14.6 kern.osproductversion: 11.4 kern.osproductversioncompat: 10.16 kern.system_version_compat: 0 vm.shared_region_version: 3 net.inet.igmp.default_version: 3 net.inet6.ip6.kame_version: 2009/apple-darwin net.mpklog.version: 1 net.smb.fs.version: 305000 hw.optional.amx_version: 2 security.mac.asp.active_rule_version: 13841998261707076720 sysctl -a | grep M1 machdep.cpu.brand_string: Apple M1 (lldb) memory read --outfile /tmp/mem.txt 0xfe0013094000 0xfe0013094000+10 --force PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace. Stack dump: 0. Program arguments: /Applications/Xcode-beta.app/Contents/Developer/usr/bin/lldb -c /Users/xss/Downloads/2021-04-30-093605.kernel.core 0 lldb 0x000104a9ce48 llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 52 1 lldb 0x000104a9c414 llvm::sys::RunSignalHandlers() + 128 2 lldb 0x000104a9d66c SignalHandler(int) + 292 3 libsystem_platform.dylib 0x00019c56ec44 _sigtramp + 56 4 LLDB 0x000105137b00 lldb_private::NativeFile::Write(void const*, unsigned long&) + 232 5 LLDB 0x0001050e7360 lldb_private::StreamFile::WriteImpl(void const*, unsigned long) + 40 6 LLDB 0x0001052a04c4 lldb_private::Stream::Printf(char const*, ...) + 124 7 LLDB 0x0001050aa644 lldb_private::DumpDataExtractor(lldb_private::DataExtractor const&, lldb_private::Stream*, unsigned long long, lldb::Format, unsigned long, unsigned long, unsigned long, unsigned long long, unsigned int, unsigned int, lldb_private::ExecutionContextScope*) + 1240 8 LLDB 0x000105621078 CommandObjectMemoryRead::DoExecute(lldb_private::Args&, lldb_private::CommandReturnObject&) + 6712 9 LLDB 0x00010516af2c lldb_private::CommandObjectParsed::Execute(char const*, lldb_private::CommandReturnObject&) + 404 10 LLDB 0x000105162370 lldb_private::CommandInterpreter::HandleCommand(char const*, lldb_private::LazyBool, lldb_private::CommandReturnObject&, lldb_private::ExecutionContext*, bool, bool) + 2264 11 LLDB 0x000105166284 lldb_private::CommandInterpreter::IOHandlerInputComplete(lldb_private::IOHandler&, std::__1::basic_string, std::__1::allocator >&) + 616 12 LLDB 0x0001050b6bac lldb_private::IOHandlerEditline::Run() + 316 13 LLDB 0x00010509f6c8 lldb_private::Debugger::RunIOHandlers() + 140 14 LLDB 0x000105167264 lldb_private::CommandInterpreter::RunCommandInterpreter(lldb_private::CommandInterpreterRunOptions&) + 160 15 LLDB 0x000104e93bf8 lldb::SBDebugger::RunCommandInterpreter(bool, bool) + 192 16 lldb 0x000104a843d8 Driver::MainLoop() + 2452 17 lldb 0x000104a85b3c main + 1880 18 libdyld.dylib0x00019c541420 start + 4 EOF -- 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 50194] New: Wrong output of llvm-config --system-libs
https://bugs.llvm.org/show_bug.cgi?id=50194 Bug ID: 50194 Summary: Wrong output of llvm-config --system-libs Product: Build scripts Version: 11.0 Hardware: PC OS: OpenBSD Status: NEW Severity: normal Priority: P Component: cmake Assignee: unassignedb...@nondot.org Reporter: vinc...@rischmann.fr CC: llvm-bugs@lists.llvm.org Created attachment 24818 --> https://bugs.llvm.org/attachment.cgi?id=24818&action=edit cmake function patch Hello, I built LLVM 12 from the release/12.x branch on OpenBSD 6.9, the output of the command `llvm-config --system-libs` is wrong, I get this: -lpthread -lm -lz.so.5.0 -lcurses.so.14.0 It should be this: -lpthread -lm -lz -lcurses I've found that it can be fixed by changing the get_library_name cmake function (https://github.com/llvm/llvm-project/blob/release/12.x/llvm/cmake/modules/GetLibraryName.cmake) with the attached patch. I don't know if this is the proper way to fix this, I've only been able to test it on openbsd and linux. -- 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 50195] New: Bindings/Go/go.test fails - lld flag treatment
https://bugs.llvm.org/show_bug.cgi?id=50195 Bug ID: 50195 Summary: Bindings/Go/go.test fails - lld flag treatment Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Core LLVM classes Assignee: unassignedb...@nondot.org Reporter: u...@polymagelabs.com CC: llvm-bugs@lists.llvm.org [I couldn't find the right component to file this against. There appears to be nothing for Go bindings or even bindings?] commit 1977c53b2ae425541a0ef329ca10cc8d5cacd0cd (origin/main) Date: Wed Apr 28 11:34:45 2021 +0900 A `ninja check-all` yields this single failure. - FAIL: LLVM :: Bindings/Go/go.test (1362 of 44478) TEST 'LLVM :: Bindings/Go/go.test' FAILED Script: -- : 'RUN: at line 1'; /home/uday/llvm-project-upstream/build/bin/llvm-go go=/usr/bin/go test llvm.org/llvm/bindings/go/llvm -- Exit Code: 1 Command Output (stdout): -- FAILllvm.org/llvm/bindings/go/llvm [build failed] FAIL -- Command Output (stderr): -- go build runtime/cgo: invalid flag in go:cgo_ldflag: -fuse-ld=lld -- Failed Tests (1): LLVM :: Bindings/Go/go.test Testing Time: 35.14s Unsupported : 19076 Passed : 25341 Expectedly Failed:60 Failed : 1 -- cmake -G Ninja ../llvm-DLLVM_ENABLE_PROJECTS="mlir" -DLLVM_TARGETS_TO_BUILD="X86;NVPTX"-DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_ENABLE_LLD=ON -DLLVM_CCACHE_BUILD=ON $ /usr/bin/go version go version go1.14.12 linux/amd64 $ python --version Python 3.6.8 $ cat /etc/*release* CentOS Linux release 8.3.2011 Derived from Red Hat Enterprise Linux 8.3 NAME="CentOS Linux" VERSION="8" -- 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 33892 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in UnqualUsingDirectiveSet::addUsingDirectives
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevl...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigch...@gmail.com, eney...@google.com, llvm-...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitch...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2021-05-02 Type: Bug New issue 33892 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in UnqualUsingDirectiveSet::addUsingDirectives https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33892 Detailed Report: https://oss-fuzz.com/testcase?key=4812243674988544 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe0e8f2ff8 Crash State: UnqualUsingDirectiveSet::addUsingDirectives UnqualUsingDirectiveSet::visitScopeChain clang::Sema::CppLookupName Sanitizer: address (ASAN) Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&revision=202105010606 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4812243674988544 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
