[llvm-bugs] [Bug 47289] New: out of memory during optimized compilation
https://bugs.llvm.org/show_bug.cgi?id=47289 Bug ID: 47289 Summary: out of memory during optimized compilation Product: clang Version: 10.0 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: C++ Assignee: unassignedclangb...@nondot.org Reporter: mizve...@gmail.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Created attachment 23886 --> https://bugs.llvm.org/attachment.cgi?id=23886&action=edit automatic reproduction (zipped due to size) Including automatic reproduction due to below crash. Note that at the end, an unrelated problem with the crash reporter itself, which produces empty source name instead of "psx-bc0931.cpp", which is included in the zip file anyway. ``` LLVM error : out of memory Stack dump: 0.Program arguments: C:\PROGRA~2\MICROS~1\2019\COMMUN~1\VC\Tools\Llvm\bin\clang-cl.exe /nologo -TP <...> -m64 /DWIN32 /D_WINDOWS /D_CRT_SECURE_NO_WARNINGS /W3 /Zi /bigobj /utf-8 /Oi /GF /Gy -fdiagnostics-absolute-paths /EHsc /WX- /D_DEBUG /O1 /Os /D_HAS_ITERATOR_DEBUGGING=0 -MTd -std:c++latest /showIncludes <...> 1. parser at end of file 2.Code generation #0 0x023767f8 #1 0x7579edc2 #2 0x02369aed #3 0x00fb3612 #4 0x00fb358b clang-cl : error : clang frontend command failed due to signal (use -v to see invocation) clang version 10.0.0 Target: x86_64-pc-windows-msvc Thread model: posix InstalledDir: C:\PROGRA~2\MICROS~1\2019\COMMUN~1\VC\Tools\Llvm\bin clang-cl: note: diagnostic msg: PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script. clang-cl: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang-cl: note: diagnostic msg: psx-bc0931.sh clang-cl: note: diagnostic msg: ``` -- 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 25165 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val) && "cast() argument of incompatible type!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-08-23 Type: Bug New issue 25165 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: isa(Val) && "cast() argument of incompatible type!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25165 Detailed Report: https://oss-fuzz.com/testcase?key=4883558978813952 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-instcombine Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: isa(Val) && "cast() argument of incompatible type!" isKnownNonZero isKnownNonZero Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202005070415:202005080243 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4883558978813952 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 47290] New: FixNamespaceComments doesn't add namespace comments for trivial namespaces
https://bugs.llvm.org/show_bug.cgi?id=47290
Bug ID: 47290
Summary: FixNamespaceComments doesn't add namespace comments
for trivial namespaces
Product: clang
Version: 10.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: kuznia...@o2.pl
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Hi,
FixNamespaceComment is documented as the following:
If true, clang-format adds missing namespace end comments and fixes invalid
existing ones.
It always works when I provide invalid namespace comments, but it doesn't work
for some trivial namespaces with no comments.
# file test.cpp
namespace works_when_together {
using foo = int;
typedef int bar;
int baz;
}
namespace doesnt_work1 {
using foo = int;
}
namespace doesnt_work2 {
typedef int bar;
}
namespace doesnt_work3 {
int baz;
}
namespace doesnt_work4 {}
# OUTPUT
$ clang-format -style="{FixNamespaceComments: true}" test.cpp
namespace works_when_together {
using foo = int;
typedef int bar;
int baz;
} // namespace works_when_together
namespace doesnt_work1 {
using foo = int;
}
namespace doesnt_work2 {
typedef int bar;
}
namespace doesnt_work3 {
int baz;
}
namespace doesnt_work4 {}
TESTED on all clang-format major versions since 5 to 10.
--
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 47267] Unable to perform a constexpr float to uint bitcast
https://bugs.llvm.org/show_bug.cgi?id=47267 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)||f8e0e5db4860 Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Simon Pilgrim --- (In reply to Simon Pilgrim from comment #2) > Thanks Richard, I've raised https://reviews.llvm.org/D86398 which attempts > this rGf8e0e5db4860 -- 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 22390 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in IntExprEvaluator::VisitBinaryOperator
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 22390 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in IntExprEvaluator::VisitBinaryOperator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=22390#c2 ClusterFuzz testcase 5742979586457600 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202008220601:202008230608 If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 47291] New: 'real_dispatch_async_and_wait_f' in namespace '__tsan::__interception'; did you mean 'dispatch_async_and_wait_f'?
https://bugs.llvm.org/show_bug.cgi?id=47291 Bug ID: 47291 Summary: 'real_dispatch_async_and_wait_f' in namespace '__tsan::__interception'; did you mean 'dispatch_async_and_wait_f'? Product: compiler-rt Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: tsan Assignee: unassignedb...@nondot.org Reporter: solot...@gmail.com CC: llvm-bugs@lists.llvm.org when compiling compiler-rt with clang on arch linux [571/768][ 74%][65.731s] Building CXX object lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors_libdispatch.cpp.o FAILED: lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors_libdispatch.cpp.o /github/workspace/swift-language-git/src/build/buildbot_linux/llvm-linux-x86_64/./bin/clang++ -I/github/workspace/swift-language-git/src/llvm-project/compiler-rt/lib/tsan/.. -D_FORTIFY_SOURCE=2 -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -Wall -std=c++14 -Wno-unused-parameter -O3 -DNDEBUG -m64 -fno-lto -fPIC -fno-builtin -fno-exceptions -fomit-frame-pointer -funwind-tables -fno-stack-protector -fno-sanitize=safe-stack -fvisibility=hidden -fno-lto -O3 -gline-tables-only -Wno-gnu -Wno-variadic-macros -Wno-c99-extensions -Wno-non-virtual-dtor -fPIE -fno-rtti -msse3 -Wframe-larger-than=530 -Wglobal-constructors -fblocks --sysroot=. -MD -MT lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors_libdispatch.cpp.o -MF lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors_libdispatch.cpp.o.d -o lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors_libdispatch.cpp.o -c /github/workspace/swift-language-git/src/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_libdispatch.cpp /github/workspace/swift-language-git/src/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_libdispatch.cpp:239:1: error: no member named 'real_dispatch_async_and_wait_f' in namespace '__tsan::__interception'; did you mean 'dispatch_async_and_wait_f'? DISPATCH_INTERCEPT_SYNC_B(dispatch_async_and_wait, false) ^ /github/workspace/swift-language-git/src/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_libdispatch.cpp:182:5: note: expanded from macro 'DISPATCH_INTERCEPT_SYNC_B' REAL(name##_f)(q, &new_context, dispatch_callback_wrap); \ ^~ /github/workspace/swift-language-git/src/llvm-project/compiler-rt/lib/tsan/../interception/interception.h:171:18: note: expanded from macro 'REAL' # define REAL(x) __interception::PTR_TO_REAL(x) ^~~~ /github/workspace/swift-language-git/src/llvm-project/compiler-rt/lib/tsan/rtl/tsan_interceptors_libdispatch.cpp:236:28: note: 'dispatch_async_and_wait_f' declared here SANITIZER_WEAK_IMPORT void dispatch_async_and_wait_f( ^ 1 error generated. [572/768][ 74%][65.986s] Building CXX object lib/tsan/CMakeFiles/clang_rt.tsan_cxx-x86_64.dir/rtl/tsan_new_delete.cpp.o [573/768][ 74%][70.809s] Building CXX object lib/tsan/CMakeFiles/clang_rt.tsan-x86_64.dir/rtl/tsan_interceptors_posix.cpp.o ninja: build stopped: subcommand failed. [4163/4166][ 99%][10245.762s] Copying llvm-locstats into /github/workspace/swift-language-git/src/build/buildbot_linux/llvm-linux-x86_64/./bin FAILED: tools/clang/runtime/compiler-rt-stamps/compiler-rt-build cd /github/workspace/swift-language-git/src/build/buildbot_linux/llvm-linux-x86_64/tools/clang/runtime/compiler-rt-bins && /usr/bin/cmake --build . && /usr/bin/cmake -E touch /github/workspace/swift-language-git/src/build/buildbot_linux/llvm-linux-x86_64/tools/clang/runtime/compiler-rt-stamps//compiler-rt-build ninja: build stopped: subcommand failed. ERROR: command terminated with a non-zero exit status 1, aborting Building the standard library for: swift-stdlib-linux-x86_64 Running Swift tests for: check-swift-all-linux-x86_64 check-swift-all-optimize-linux-x86_64 ERROR: command terminated with a non-zero exit status 1, aborting ==> ERROR: A failure occurred in build(). Aborting... -- 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 25182 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !Result || (LHS.isSentinel() && LHS.Inst == RHS.Inst) || getHashValueImpl(LHS) =
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-08-23 Type: Bug New issue 25182 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !Result || (LHS.isSentinel() && LHS.Inst == RHS.Inst) || getHashValueImpl(LHS) = https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25182 Detailed Report: https://oss-fuzz.com/testcase?key=6585296744087552 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-opt-fuzzer--x86_64-earlycse Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: !Result || (LHS.isSentinel() && LHS.Inst == RHS.Inst) || getHashValueImpl(LHS) = llvm::DenseMapInfo::isEqual bool llvm::DenseMapBasehttps://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&revision=202008230608 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6585296744087552 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 47136] Regression (in LSV?) due to changes in InstCombine
https://bugs.llvm.org/show_bug.cgi?id=47136 bjorn.a.petters...@ericsson.com changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||ec06b381304140b2553cfdfae5a ||063f39c5c59ff Status|NEW |RESOLVED --- Comment #17 from bjorn.a.petters...@ericsson.com --- The regression was solved by https://reviews.llvm.org/rGec06b381304140b2553cfdfae5a063f39c5c59ff For info: Haven't see any benefits from updating ScalarEvolution (such as proposed in https://reviews.llvm.org/D85969) given the changed canonicalization in instcombine (given current phase ordering in my O3 pipeline). So that patch is abandoned (at least until someone finds it useful). -- 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 47292] New: ICE in polly with -O3
https://bugs.llvm.org/show_bug.cgi?id=47292 Bug ID: 47292 Summary: ICE in polly with -O3 Product: Polly Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Optimizer Assignee: polly-...@googlegroups.com Reporter: vsevolod.livins...@frtk.ru CC: llvm-bugs@lists.llvm.org The error is non-deterministic. The crash backtrace varies a lot from run to run. >$ clang++ -mllvm -polly -O3 -c func.cpp clang++: llvm-trunk/polly/include/polly/ScopInfo.h:1387: llvm::Loop* polly::ScopStmt::getSurroundingLoop() const: Assertion `!isCopyStmt() && "No surrounding loop for artificially created statements"' 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: clang++ -mllvm -polly -O3 -c func.cpp 1. parser at end of file 2. Per-module optimization passes 3. Running pass 'Function Pass Manager' on module 'func.cpp'. 4. Running pass 'Region Pass Manager' on function '@_Z4testxatjshxbaPtPA2_x' 5. Running pass 'Polly - Simplify' on basic block '%entry.split' #0 0x5600b983e95e llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/clang-12+0x1e1095e) #1 0x5600b983c6c4 llvm::sys::RunSignalHandlers() (/clang-12+0x1e0e6c4) #2 0x5600b983c941 llvm::sys::CleanupOnSignal(unsigned long) (/clang-12+0x1e0e941) #3 0x5600b97aa988 CrashRecoverySignalHandler(int) (/clang-12+0x1d7c988) #4 0x7f6d14d223c0 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x153c0) #5 0x7f6d147ae18b raise /build/glibc-YYA7BZ/glibc-2.31/signal/../sysdeps/unix/sysv/linux/raise.c:51:1 #6 0x7f6d1478d859 abort /build/glibc-YYA7BZ/glibc-2.31/stdlib/abort.c:81:7 #7 0x7f6d1478d729 get_sysdep_segment_value /build/glibc-YYA7BZ/glibc-2.31/intl/loadmsgcat.c:509:8 #8 0x7f6d1478d729 _nl_load_domain /build/glibc-YYA7BZ/glibc-2.31/intl/loadmsgcat.c:970:34 #9 0x7f6d1479ef36 (/lib/x86_64-linux-gnu/libc.so.6+0x36f36) #10 0x5600ba93353f polly::markReachable(polly::Scop*, llvm::LoopInfo*, llvm::DenseSet >&, llvm::DenseSet >&, polly::ScopStmt*) (/clang-12+0x2f0553f) #11 0x5600ba8721e3 (anonymous namespace)::Simplify::markAndSweep(llvm::LoopInfo*) (/clang-12+0x2e441e3) #12 0x5600ba875be8 (anonymous namespace)::Simplify::runOnScop(polly::Scop&) (/clang-12+0x2e47be8) #13 0x5600b8a5c170 llvm::RGPassManager::runOnFunction(llvm::Function&) (/clang-12+0x102e170) #14 0x5600b9174301 llvm::FPPassManager::runOnFunction(llvm::Function&) (/clang-12+0x1746301) #15 0x5600b91749f9 llvm::FPPassManager::runOnModule(llvm::Module&) (/clang-12+0x17469f9) #16 0x5600b917349c llvm::legacy::PassManagerImpl::run(llvm::Module&) (/clang-12+0x174549c) #17 0x5600b9af4109 (anonymous namespace)::EmitAssemblyHelper::EmitAssembly(clang::BackendAction, std::unique_ptr >) (/clang-12+0x20c6109) #18 0x5600b9af5bf5 clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::HeaderSearchOptions const&, clang::CodeGenOptions const&, clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout const&, llvm::Module*, clang::BackendAction, std::unique_ptr >) (/clang-12+0x20c7bf5) #19 0x5600ba7d9891 clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) (/clang-12+0x2dab891) #20 0x5600bb91b5a9 clang::ParseAST(clang::Sema&, bool, bool) (/clang-12+0x3eed5a9) #21 0x5600ba7d82d8 clang::CodeGenAction::ExecuteAction() (/clang-12+0x2daa2d8) #22 0x5600ba124a59 clang::FrontendAction::Execute() (/clang-12+0x26f6a59) #23 0x5600ba0db176 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/clang-12+0x26ad176) #24 0x5600ba1f8690 clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/clang-12+0x27ca690) #25 0x5600b85fe296 cc1_main(llvm::ArrayRef, char const*, void*) (/clang-12+0xbd0296) #26 0x5600b85fb5e8 ExecuteCC1Tool(llvm::SmallVectorImpl&) (/clang-12+0xbcd5e8) #27 0x5600b9f9a919 void llvm::function_ref::callback_fn >, std::__cxx11::basic_string, std::allocator >*, bool*) const::'lambda'()>(long) (/clang-12+0x256c919) #28 0x5600b97aab0c llvm::CrashRecoveryContext::RunSafely(llvm::function_ref) (/clang-12+0x1d7cb0c) #29 0x5600b9f9b236 clang::driver::CC1Command::Execute(llvm::ArrayRef >, std::__cxx11::basic_string, std::allocator >*, bool*) const (.part.0) (/clang-12+0x256d236) #30 0x5600b9f71e1c clang::driver::Compilation::ExecuteCommand(clang::driver::Command const&, clang::driver::Command const*&) const (/clang-12+0x2543e1c) #31 0x5600b9f72756 clang::driver::Compilation::ExecuteJobs(clang::driver::JobList const&, llvm::SmallVectorImpl >&) const (/clang-12+0x2544756) #32 0x5600b9f7be49 clang::driver::Driver::ExecuteCompilation(clang::driver::Compilation&, llvm::SmallVectorImpl >&) (/clang-12+0x254de49) #33 0x5600b8578
[llvm-bugs] [Bug 47255] clang-format needs to run twice
https://bugs.llvm.org/show_bug.cgi?id=47255 Jake Merdich changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED CC||jake.merd...@amd.com --- Comment #1 from Jake Merdich --- Pretty sure this is a dupe of pr43845, which was fixed for clang 11. I reproduced this from 10.x and not the latest code in any case. *** This bug has been marked as a duplicate of bug 43845 *** -- 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 47293] New: Merge 2b37174b9a5db235e493cb72e4454cc08a1b179 into 11.0
https://bugs.llvm.org/show_bug.cgi?id=47293 Bug ID: 47293 Summary: Merge 2b37174b9a5db235e493cb72e4454cc08a1b179 into 11.0 Product: clang Version: 11.0 Hardware: All OS: OpenBSD Status: NEW Severity: release blocker Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: b...@comstyle.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Blocks: 46725 Please merge https://github.com/llvm/llvm-project/commit/2b37174b9a5db235e493cb72e4454cc08a1b1791. [clang][Driver] Implement AddClangSystemIncludeArgs and HasNativeLLVMSupport for the OpenBSD clang driver. If not overridden, AddClangSystemIncludeArgs's implementation is empty, so by default, no system include args are added to the Clang driver. This means that invoking Clang without the frontend must include a manual -I/usr/include flag, which is inconsistent behavior. Therefore, override and implement this method to match. Some boilerplate is also borrowed for handling of the other driver flags. While we are here, also override and enable HasNativeLLVMSupport. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=46725 [Bug 46725] [meta] 11.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 47294] New: Merge bf3577ef64c300ba7841a90a4e09e1e305271976 into 11.0
https://bugs.llvm.org/show_bug.cgi?id=47294 Bug ID: 47294 Summary: Merge bf3577ef64c300ba7841a90a4e09e1e305271976 into 11.0 Product: clang Version: 11.0 Hardware: All OS: OpenBSD Status: NEW Severity: release blocker Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: b...@comstyle.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Blocks: 46725 Please merge https://github.com/llvm/llvm-project/commit/bf3577ef64c300ba7841a90a4e09e1e305271976. [clang][Driver] Implement addLibCxxIncludePaths and getCompilerRT for the OpenBSD clang driver. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=46725 [Bug 46725] [meta] 11.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 25184 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: Num < NumOperands && "Invalid child # of SDNode!"
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2020-08-24 Type: Bug New issue 25184 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: ASSERT: Num < NumOperands && "Invalid child # of SDNode!" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25184 Detailed Report: https://oss-fuzz.com/testcase?key=5672260382490624 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: Num < NumOperands && "Invalid child # of SDNode!" combineStore llvm::X86TargetLowering::PerformDAGCombine Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202008190617:202008200618 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5672260382490624 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
