[llvm-bugs] [Bug 19745] '--no-add-needed' is added to the linker flags for all versions of RHEL
https://bugs.llvm.org/show_bug.cgi?id=19745
Fangrui Song changed:
What|Removed |Added
Status|NEW |RESOLVED
CC||i...@maskray.me
Resolution|--- |FIXED
--- Comment #3 from Fangrui Song ---
> '--no-add-needed' is the default only since RHEL7
gcc doesn't add the option. I think it is just that before binutils 2.22,
--add-needed was the default.
Just deleted
if (Distro.IsRedhat() && Distro != Distro::RHEL5 && Distro != Distro::RHEL6)
ExtraOpts.push_back("--no-add-needed");
in r365877
--
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 42517] CodeGenCXX/cxx2a-compare.cpp fails on x86 Linux after r363952
https://bugs.llvm.org/show_bug.cgi?id=42517 Luke 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 42487] Headers/max_align.c fails on Linux x86
https://bugs.llvm.org/show_bug.cgi?id=42487 Luke changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Luke --- Verified FIXED with r365558. All lit tests are now passing in Arch 32. Thanks Jason and Andus! -- 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 42594] New: clang crash in ASTContext::getPointerType
https://bugs.llvm.org/show_bug.cgi?id=42594 Bug ID: 42594 Summary: clang crash in ASTContext::getPointerType Product: new-bugs Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: llvmb...@squelart.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Created attachment 22233 --> https://bugs.llvm.org/attachment.cgi?id=22233&action=edit zip of source and script part 1 Backtrace: 0:10.79 #0 0x7ff7f0e16f10 clang::ASTContext::getPointerType(class clang::QualType)const (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x26a6f10) 0:10.79 #1 0x7ff7f0e16f3d clang::ASTContext::getPointerType(class clang::QualType)const (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x26a6f3d) 0:10.79 #2 0x7ff7f09b65e2 clang::Sema::getCurrentThisType(void) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x22465e2) 0:10.79 #3 0x7ff7f0a0d42d clang::Sema::ActOnIdExpression(class clang::Scope *,class clang::CXXScopeSpec &,class clang::SourceLocation,class clang::UnqualifiedId &,bool,bool,class std::unique_ptr >,bool,class clang::Token *) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x229d42d) 0:10.79 #4 0x7ff7f06b5155 clang::Parser::ParseCastExpression(bool,bool,bool &,enum clang::Parser::TypeCastState,bool) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f45155) 0:10.79 #5 0x7ff7f06aca93 clang::Parser::ParseAssignmentExpression(enum clang::Parser::TypeCastState) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f3ca93) 0:10.79 #6 0x7ff7f06ac995 clang::Parser::ParseExpression(enum clang::Parser::TypeCastState) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f3c995) 0:10.79 #7 0x7ff7f069f2d3 clang::Parser::ParseExprStatement(void) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2f2d3) 0:10.79 #8 0x7ff7f069d431 clang::Parser::ParseStatementOrDeclarationAfterAttributes(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *,struct clang::Parser::ParsedAttributesWithRange &) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2d431) 0:10.79 #9 0x7ff7f069ceec clang::Parser::ParseStatementOrDeclaration(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2ceec) 0:10.79 #10 0x7ff7f06a5c3c clang::Parser::ParseCompoundStatementBody(bool) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f35c3c) 0:10.79 #11 0x7ff7f069d4be clang::Parser::ParseStatementOrDeclarationAfterAttributes(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *,struct clang::Parser::ParsedAttributesWithRange &) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2d4be) 0:10.80 #12 0x7ff7f069ceec clang::Parser::ParseStatementOrDeclaration(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2ceec) 0:10.80 #13 0x7ff7f06a10b9 clang::Parser::ParseIfStatement(class clang::SourceLocation *) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f310b9) 0:10.80 #14 0x7ff7f069d6ad clang::Parser::ParseStatementOrDeclarationAfterAttributes(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *,struct clang::Parser::ParsedAttributesWithRange &) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2d6ad) 0:10.80 #15 0x7ff7f069ceec clang::Parser::ParseStatementOrDeclaration(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2ceec) 0:10.80 #16 0x7ff7f06a5c3c clang::Parser::ParseCompoundStatementBody(bool) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f35c3c) 0:10.80 #17 0x7ff7f069d4be clang::Parser::ParseStatementOrDeclarationAfterAttributes(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *,struct clang::Parser::ParsedAttributesWithRange &) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2d4be) 0:10.80 #18 0x7ff7f069ceec clang::Parser::ParseStatementOrDeclaration(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f2ceec) 0:10.80 #19 0x7ff7f06a10b9 clang::Parser::ParseIfStatement(class clang::SourceLocation *) (c:\Users\GERALD~1\MOZBUI~1\clang\bin\clang-cl.exe+0x1f310b9) 0:10.80 #20 0x7ff7f069d6ad clang::Parser::ParseStatementOrDeclarationAfterAttributes(class llvm::SmallVector &,enum clang::Parser::AllowedConstructsKind,class clang::SourceLocation *,struct clang::Parser::ParsedAttr
[llvm-bugs] [Bug 9825] Need both -fno-omit-frame-pointer and -mno-omit-leaf-frame-pointer to get a fp on linux on a leaf function
https://bugs.llvm.org/show_bug.cgi?id=9825 Fangrui Song changed: What|Removed |Added CC||i...@maskray.me Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Fangrui Song --- Fixed by D64294/r365860. -- 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 41094] want -fomit-frame-pointer by default on PowerPC
https://bugs.llvm.org/show_bug.cgi?id=41094 Fangrui Song changed: What|Removed |Added CC||i...@maskray.me Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Fangrui Song --- I think this is just the gcc default, it doesn't have the OS-varying behavior. Fixed by r365862 -- 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 15752 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-07-12 Type: Bug New issue 15752 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15752 Detailed report: https://oss-fuzz.com/testcase?key=5642957929054208 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe0c081bf8 Crash State: clang::DiagnosticIDs::isUnrecoverable clang::DiagnosticIDs::ProcessDiag clang::DiagnosticsEngine::EmitCurrentDiagnostic Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201907080311:201907090313 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5642957929054208 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. -- 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 42593] New: apt.llvm.org packages haven't been updated for a few days
https://bugs.llvm.org/show_bug.cgi?id=42593 Bug ID: 42593 Summary: apt.llvm.org packages haven't been updated for a few days Product: Packaging Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: deb packages Assignee: unassignedb...@nondot.org Reporter: zeratul...@hotmail.com CC: llvm-bugs@lists.llvm.org As of the time of this filing (July 11), the dates of the most recent packages are all at least a week old. For example: Xenial (16.04): June 21 Bionic (18.04): July 3 Debian stable: July 3 Looking at Jenkins, the jobs are running, but they're failing. Here are some example logs: https://llvm-jenkins.debian.net/job/llvm-toolchain-xenial-binaries/1774/architecture=amd64,distribution=xenial/console https://llvm-jenkins.debian.net/job/llvm-toolchain-bionic-binaries/850/architecture=amd64,distribution=bionic/console It's not clear to me from the logs what is actually failing. -- 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 17523] Config failed to check for libxml
https://bugs.llvm.org/show_bug.cgi?id=17523 J. Ryan Stinnett changed: What|Removed |Added CC||jry...@gmail.com Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from J. Ryan Stinnett --- The autoconf build system has now been removed, and the CMake build system that replaces it appears to properly check for libxml, so I believe this is fixed. Please reopen if I have misunderstood. -- 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 42577] Build is failing while compiling using clang++ language with flags -fprofile-instr-generate -fcoverage-mapping
https://bugs.llvm.org/show_bug.cgi?id=42577 Zhizhou Yang changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Zhizhou Yang --- This is fixed on llvm trunk (https://reviews.llvm.org/D61138). For ChromeOS, we are tracking this issue in: https://bugs.chromium.org/p/chromium/issues/detail?id=958882 This should be fixed in a few days after we roll the new compiler. Please follow the bug above for updates. -- 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 42592] New: ICE: "Expected VPlan CFG to terminate with branch in NativePath" with -O3 -march=skx -mllvm -enable-vplan-native-path
https://bugs.llvm.org/show_bug.cgi?id=42592
Bug ID: 42592
Summary: ICE: "Expected VPlan CFG to terminate with branch in
NativePath" with -O3 -march=skx -mllvm
-enable-vplan-native-path
Product: new-bugs
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: vsevolod.livins...@frtk.ru
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
Clang fails with ICE with -O3 -march=skx -mllvm -enable-vplan-native-path
options. This happens every time it tries to vectorize something, so it
prevents further testing.
Reproducer:
extern unsigned int a[100], b[100], c[100] [100];
void foo () {
for (int i = 0; i < 100; ++i)
for (int j = 0; j < 100; ++j)
a[i] += b[i] + c[i][j];
}
Error:
>$ clang -c -O3 -march=skx -mllvm -enable-vplan-native-path small.c
clang-8: /llvm/llvm-8.0/lib/Transforms/Vectorize/VPlan.cpp:426: void
llvm::VPlan::execute(llvm::VPTransformState*): Assertion
`(!EnableVPlanNativePath || isa(LastBB->getTerminator())) &&
"Expected VPlan CFG to terminate with branch in NativePath"' failed.
Stack dump:
0. Program arguments: /llvm/bin-8.0/bin/clang-8 -cc1 -triple
x86_64-unknown-linux-gnu -emit-obj -disable-free -main-file-name repr.c
-mrelocation-model static -mthread-model posix -fmath-errno -masm-verbose
-mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu skx
-dwarf-column-info -debugger-tuning=gdb -momit-leaf-frame-pointer
-coverage-notes-file
/yarpgen/testing/result/clang/compfail/S_1031252889/repr.gcno -resource-dir
/llvm/bin-8.0/lib/clang/8.0.0 -internal-isystem /usr/local/include
-internal-isystem /llvm/bin-8.0/lib/clang/8.0.0/include
-internal-externc-isystem /include -internal-externc-isystem /usr/include -O3
-fdebug-compilation-dir /yarpgen/testing/result/clang/compfail/S_1031252889
-ferror-limit 19 -fmessage-length 190 -fobjc-runtime=gcc
-fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp
-mllvm -enable-vplan-native-path -o repr.o -x c repr.c -faddrsig
1. parser at end of file
2. Per-module optimization passes
3. Running pass 'Function Pass Manager' on module 'repr.c'.
4. Running pass 'Loop Vectorization' on function '@foo'
#0 0x01c8dd1a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x1c8dd1a)
#1 0x01c8bcd4 llvm::sys::RunSignalHandlers()
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x1c8bcd4)
#2 0x01c8be02 SignalHandler(int)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x1c8be02)
#3 0x7f0d42a975d0 __restore_rt (/lib64/libpthread.so.0+0xf5d0)
#4 0x7f0d41686207 __GI_raise (/lib64/libc.so.6+0x36207)
#5 0x7f0d416878f8 __GI_abort (/lib64/libc.so.6+0x378f8)
#6 0x7f0d4167f026 __assert_fail_base (/lib64/libc.so.6+0x2f026)
#7 0x7f0d4167f0d2 (/lib64/libc.so.6+0x2f0d2)
#8 0x01e0869c llvm::VPlan::execute(llvm::VPTransformState*)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x1e0869c)
#9 0x01dcab01
llvm::LoopVectorizationPlanner::executePlan(llvm::InnerLoopVectorizer&,
llvm::DominatorTree*) (/localdisk2/llvm/bin-8.0/bin/clang-8+0x1dcab01)
#10 0x01dd294c llvm::LoopVectorizePass::processLoop(llvm::Loop*)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x1dd294c)
#11 0x01dd3a59 llvm::LoopVectorizePass::runImpl(llvm::Function&,
llvm::ScalarEvolution&, llvm::LoopInfo&, llvm::TargetTransformInfo&,
llvm::DominatorTree&, llvm::BlockFrequencyInfo&, llvm::TargetLibraryInfo*,
llvm::DemandedBits&, llvm::AAResults&, llvm::AssumptionCache&,
std::function&,
llvm::OptimizationRemarkEmitter&) (/llvm/bin-8.0/bin/clang-8+0x1dd3a59)
#12 0x01dd3c50 (anonymous
namespace)::LoopVectorize::runOnFunction(llvm::Function&)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x1dd3c50)
#13 0x017444e8 llvm::FPPassManager::runOnFunction(llvm::Function&)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x17444e8)
#14 0x01744599 llvm::FPPassManager::runOnModule(llvm::Module&)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x1744599)
#15 0x0174394f llvm::legacy::PassManagerImpl::run(llvm::Module&)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x174394f)
#16 0x01e6837f 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 >)
(/llvm/bin-8.0/bin/clang-8+0x1e6837f)
#17 0x0275ae78
clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x275ae78)
#18 0x02f81649 clang::ParseAST(clang::Sema&, bool, bool)
(/localdisk2/llvm/bin-8.0/bin/clang-8+0x2f81649)
#19 0x02759ef8 clang::CodeGenAction::ExecuteAction()
(/localdisk
[llvm-bugs] Issue 15749 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-guard_widening: Use-of-uninitialized-value in initStream
Updates: Labels: Fuzz-Blocker Comment #1 on issue 15749 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-guard_widening: Use-of-uninitialized-value in initStream https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15749#c1 This crash occurs very frequently on linux platform and is likely preventing the fuzzer llvm-opt-fuzzer--x86_64-guard_widening from making much progress. Fixing this will allow more bugs to be found. 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 42591] New: LLVM doesn't compile with Visual Studio 2017 Express edition: missing atlbase.h
https://bugs.llvm.org/show_bug.cgi?id=42591 Bug ID: 42591 Summary: LLVM doesn't compile with Visual Studio 2017 Express edition: missing atlbase.h Product: Build scripts Version: 8.0 Hardware: PC OS: Windows XP Status: NEW Severity: enhancement Priority: P Component: autoconf Assignee: unassignedb...@nondot.org Reporter: mike.ri...@gmail.com CC: llvm-bugs@lists.llvm.org I ran into an issue when attempting to compile LLVM on Windows 10 using the Visual Studio 2017 Express edition. Express edition does not come with ATL support, and several files have a dependency on atlbase.h. It is possible to install ATL for 2017 as part of the Visual Studio Build Tools ["C++ ATL for for v141 build tools (x86 & x64)"]. But only Build Tools 2019 is available, and the ATL header/lib files get installed in the "C:\Program Files (x86)\Microsoft Visual Studio\2019" not "...2017" directory. The CL compiler can't find them in that non-standard location. This problem is fixed by using Visual Studio 2017 Community Edition or higher, which have ATL support build-in. But unfortunately the Express edition is the only version that allows for free commercial use. Is it possible to make LLVM independent of ATL when it's not available? If no, I suggest you modify your Getting Started guide (https://llvm.org/docs/GettingStarted.html) to mention that VS Express Edition is not supported. Compile log snip... C:\build\2017\llvm>cmake --build . --config Release Microsoft (R) Build Engine version 15.9.21+g9802d43bc3 for .NET Framework Copyright (C) Microsoft Corporation. All rights reserved. etc... DIAEnumSourceFiles.cpp v:\llvm-project\llvm\include\llvm\debuginfo\pdb\dia\DIASupport.h(25): fatal error C1083: Cannot open include file: 'atl base.h': No such file or directory (compiling source file V:\llvm-project\llvm\lib\DebugInfo\PDB\DIA\DIAEnumFrameData.c pp) [C:\build\2017\llvm\lib\DebugInfo\PDB\LLVMDebugInfoPDB.vcxproj] v:\llvm-project\llvm\include\llvm\debuginfo\pdb\dia\DIASupport.h(25): fatal error C1083: Cannot open include file: 'atl base.h': No such file or directory (compiling source file V:\llvm-project\llvm\lib\DebugInfo\PDB\DIA\DIADataStream.cpp) [C:\build\2017\llvm\lib\DebugInfo\PDB\LLVMDebugInfoPDB.vcxproj] v:\llvm-project\llvm\include\llvm\debuginfo\pdb\dia\DIASupport.h(25): fatal error C1083: Cannot open include file: 'atl base.h': No such file or directory (compiling source file V:\llvm-project\llvm\lib\DebugInfo\PDB\DIA\DIAEnumDebugStream s.cpp) [C:\build\2017\llvm\lib\DebugInfo\PDB\LLVMDebugInfoPDB.vcxproj] v:\llvm-project\llvm\include\llvm\debuginfo\pdb\dia\DIASupport.h(25): fatal error C1083: Cannot open include file: 'atl base.h': No such file or directory (compiling source file V:\llvm-project\llvm\lib\DebugInfo\PDB\DIA\DIAEnumInjectedSou rces.cpp) [C:\build\2017\llvm\lib\DebugInfo\PDB\LLVMDebugInfoPDB.vcxproj] v:\llvm-project\llvm\include\llvm\debuginfo\pdb\dia\DIASupport.h(25): fatal error C1083: Cannot open include file: 'atl base.h': No such file or directory (compiling source file V:\llvm-project\llvm\lib\DebugInfo\PDB\DIA\DIAEnumSectionCont ribs.cpp) [C:\build\2017\llvm\lib\DebugInfo\PDB\LLVMDebugInfoPDB.vcxproj] v:\llvm-project\llvm\include\llvm\debuginfo\pdb\dia\DIASupport.h(25): fatal error C1083: Cannot open include file: 'atl base.h': No such file or directory (compiling source file V:\llvm-project\llvm\lib\DebugInfo\PDB\DIA\DIAEnumLineNumbers .cpp) [C:\build\2017\llvm\lib\DebugInfo\PDB\LLVMDebugInfoPDB.vcxproj] v:\llvm-project\llvm\include\llvm\debuginfo\pdb\dia\DIASupport.h(25): fatal error C1083: Cannot open include file: 'atl base.h': No such file or directory (compiling source file V:\llvm-project\llvm\lib\DebugInfo\PDB\DIA\DIAEnumSourceFiles .cpp) [C:\build\2017\llvm\lib\DebugInfo\PDB\LLVMDebugInfoPDB.vcxproj] DIAEnumSymbols.cpp -- 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 42590] New: [AMDGPU][MC] Incorrect detection of unsupported instructions on errors
https://bugs.llvm.org/show_bug.cgi?id=42590 Bug ID: 42590 Summary: [AMDGPU][MC] Incorrect detection of unsupported instructions on errors Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: AMDGPU Assignee: unassignedb...@nondot.org Reporter: dpreobrazhen...@luxoft.com CC: llvm-bugs@lists.llvm.org Assembler often reports an operand error when the actual reason is that instruction is not supported. For example, the following instruction is not supported on GFX8, but assembler issues an "invalid operand" error: v_swap_b32 v1, 0 A related problem is that when assembler do report "instruction not supported on this GPU", it may also be incorrect. These errors are caused by unsupported operands or their combinations. For example: v_add_co_ci_u32_e32 v3, vcc_lo, v3, v4, vcc_lo When this instruction is assembled for GFX10 with wavesize=64, assembler incorrectly reports that the instruction is not supported which is not the case. -- 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 15749 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-guard_widening: Use-of-uninitialized-value in initStream
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.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-MemorySanitizer Unreproducible Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-Medium Reported-2019-07-11 Type: Bug-Security New issue 15749 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-guard_widening: Use-of-uninitialized-value in initStream https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15749 Detailed report: https://oss-fuzz.com/testcase?key=5731751848050688 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-guard_widening Fuzz target binary: llvm-opt-fuzzer--x86_64-guard_widening Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Use-of-uninitialized-value Crash Address: Crash State: initStream llvm::getBitcodeFileContents llvm::getBitcodeModuleList Sanitizer: memory (MSAN) Recommended Security Severity: Medium Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5731751848050688 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days. -- 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 15748 in oss-fuzz: llvm/clang-fuzzer: Null-dereference READ in clang::Decl::AccessDeclContextSanity
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-07-11 Type: Bug New issue 15748 by ClusterFuzz-External: llvm/clang-fuzzer: Null-dereference READ in clang::Decl::AccessDeclContextSanity https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15748 Detailed report: https://oss-fuzz.com/testcase?key=5655626304192512 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: clang::Decl::AccessDeclContextSanity LookupDirect clang::Sema::LookupQualifiedName Sanitizer: memory (MSAN) Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5655626304192512 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. -- 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 42589] New: Crash when building the Linux kernel for MIPS
https://bugs.llvm.org/show_bug.cgi?id=42589 Bug ID: 42589 Summary: Crash when building the Linux kernel for MIPS Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: MIPS Assignee: unassignedb...@nondot.org Reporter: natechancel...@gmail.com CC: llvm-bugs@lists.llvm.org Original issue: https://github.com/ClangBuiltLinux/linux/issues/571 When building the file fs/ext4/ioctl.c in the Linux kernel (https://github.com/torvalds/linux/blob/v5.2/fs/ext4/ioctl.c), we see the following crash: 0. Program arguments: /usr/lib/llvm-9/bin/clang -cc1 -triple mipsel-unknown-linux-gnu -S -disable-free -disable-llvm-verifier -discard-value-names -main-file-name ioctl.c -mrelocation-model static -mthread-model posix -fno-delete-null-pointer-checks -mllvm -warn-stack-size=1024 -relaxed-aliasing -fmath-errno -masm-verbose -no-integrated-as -mconstructor-aliases -ffreestanding -fuse-init-array -target-cpu mips32r2 -target-feature +noabicalls -target-feature +soft-float -target-abi o32 -msoft-float -mfloat-abi soft -mllvm -mno-check-zero-division -mllvm -mips-ssection-threshold=0 -mllvm -mgpopt -dwarf-column-info -debugger-tuning=gdb -momit-leaf-frame-pointer -coverage-notes-file /continuous-integration/linux/fs/ext4/ioctl.gcno -nostdsysteminc -nobuiltininc -resource-dir /usr/lib/llvm-9/lib/clang/9.0.0 -isystem /usr/lib/llvm-9/lib/clang/9.0.0/include -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -I ./arch/mips/include -I ./arch/mips/include/generated -I ./include -I ./arch/mips/include/uapi -I ./arch/mips/include/generated/uapi -I ./include/uapi -I ./include/generated/uapi -D __KERNEL__ -D VMLINUX_LOAD_ADDRESS=0x8010 -D DATAOFFSET=0 -D GAS_HAS_SET_HARDFLOAT -D TOOLCHAIN_SUPPORTS_VIRT -D TOOLCHAIN_SUPPORTS_CRC -D TOOLCHAIN_SUPPORTS_DSP -D TOOLCHAIN_SUPPORTS_GINV -I ./arch/mips/include/asm/mach-malta -I ./arch/mips/include/asm/mach-generic -D KBUILD_BASENAME="ioctl" -D KBUILD_MODNAME="ext4" -O2 -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -Wno-address-of-packed-member -Wno-format-invalid-specifier -Wno-gnu -Wno-tautological-compare -Wno-unused-const-variable -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Werror=date-time -Werror=incompatible-pointer-types -Wno-initializer-overrides -Wno-unused-value -Wno-format -Wno-sign-compare -Wno-format-zero-length -Wno-uninitialized -std=gnu89 -fno-dwarf-directory-asm -fdebug-compilation-dir /continuous-integration/linux -ferror-limit 19 -fmessage-length 0 -fwrapv -stack-protector 2 -fwchar-type=short -fno-signed-wchar -fobjc-runtime=gcc -fno-common -fdiagnostics-show-option -fcolor-diagnostics -vectorize-loops -vectorize-slp -o /tmp/ioctl-501db4.s -x c fs/ext4/ioctl.c 1. parser at end of file 2. Code generation 3. Running pass 'Function Pass Manager' on module 'fs/ext4/ioctl.c'. 4. Running pass 'MIPS DAG->DAG Pattern Instruction Selection' on function '@ext4_ioctl' #0 0x7f7b606524ff llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0xb394ff) #1 0x7f7b60650940 llvm::sys::RunSignalHandlers() (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0xb37940) #2 0x7f7b60652901 (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0xb39901) #3 0x7f7b63c8f730 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12730) #4 0x7f7b61ec2753 llvm::MipsSEDAGToDAGISel::SelectInlineAsmMemoryOperand(llvm::SDValue const&, unsigned int, std::vector >&) (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0x23a9753) #5 0x7f7b60c060b7 llvm::SelectionDAGISel::SelectInlineAsmMemoryOperands(std::vector >&, llvm::SDLoc const&) (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0x10ed0b7) #6 0x7f7b60c06a14 llvm::SelectionDAGISel::Select_INLINEASM(llvm::SDNode*, bool) (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0x10eda14) #7 0x7f7b60c03ac7 llvm::SelectionDAGISel::DoInstructionSelection() (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0x10eaac7) #8 0x7f7b60c03170 llvm::SelectionDAGISel::CodeGenAndEmitDAG() (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0x10ea170) #9 0x7f7b60c02837 llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&) (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0x10e9837) #10 0x7f7b60c00226 llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0x10e7226) #11 0x7f7b61e900da llvm::MipsDAGToDAGISel::runOnMachineFunction(llvm::MachineFunction&) (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0x23770da) #12 0x7f7b608d6428 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) (/usr/lib/x86_64-linux-gnu/libLLVM-9.so.1+0xdbd428) #13 0x7f7b6074ecf6 llvm::FPPassManager::runOnFunction(llvm::Function&) (/usr/lib/x86_64-li
[llvm-bugs] Issue 15747 in oss-fuzz: llvm/clang-fuzzer: Null-dereference READ in clang::Sema::getCurBlock
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-07-11 Type: Bug New issue 15747 by ClusterFuzz-External: llvm/clang-fuzzer: Null-dereference READ in clang::Sema::getCurBlock https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15747 Detailed report: https://oss-fuzz.com/testcase?key=5749121803091968 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x Crash State: clang::Sema::getCurBlock clang::Sema::makeTypoCorrectionConsumer clang::Sema::CorrectTypoDelayed Sanitizer: memory (MSAN) Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5749121803091968 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. -- 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 42588] New: DEB package http://apt.llvm.org/bionic/pool/main/l/llvm-toolchain-8/libc%2b%2babi-8-dev_8.0.1~svn363027-1~exp1~20190611211629.77_amd64.deb is broken, it contains invalid l
https://bugs.llvm.org/show_bug.cgi?id=42588 Bug ID: 42588 Summary: DEB package http://apt.llvm.org/bionic/pool/main/l/llvm-toolchain- 8/libc%2b%2babi-8-dev_8.0.1~svn363027-1~exp1~201906112 11629.77_amd64.deb is broken, it contains invalid libc++abi.a with lenght 165 Product: Packaging Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: deb packages Assignee: unassignedb...@nondot.org Reporter: andrei.aleksee...@gmail.com CC: llvm-bugs@lists.llvm.org -- 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 42587] New: ICE on missing ... of operator sizeof... at trailing return type for lambda
https://bugs.llvm.org/show_bug.cgi?id=42587
Bug ID: 42587
Summary: ICE on missing ... of operator sizeof... at trailing
return type for lambda
Product: new-bugs
Version: 6.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: agate.p...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
clang++ crash with segmentation fault if ... of operator sizeof... forgotten at
trailing return type of lambda.
template < int > class ct {};
int main() {
[](auto... args) -> ct< sizeof(args) >{}();
}
https://wandbox.org/permlink/yW6TCpJqvqTx0EKw
This is regression from clang 6.0.0. I confirmed that it also occurs at 6.0.1,
7.0.0, 8.0.0 and 9.0.0.
clang 5.0.0 produces the following expected error message:
prog.cc:8:5: error: expected expression
[](auto... args) -> ct< sizeof(args) >{}();
Here is valid code. (This code produce an warning.)
template < int > class ct {};
int main() {
[](auto... args) -> ct< sizeof...(args) >{}();
}
Also, the following code replaces the lambda of the above program with a
function template. This program correctly outputs an expected error.
template < int > class ct {};
template < typename... Args >
auto ft(Args... args) -> ct< sizeof(args) > {}
int main() {
ft();
}
Stack dump:
0. Program arguments: /opt/wandbox/clang-head/bin/clang-9 -cc1 -triple
x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free
-disable-llvm-verifier -discard-value-names -main-file-name prog.cc
-mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno
-masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array
-target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -nostdinc++
-resource-dir /opt/wandbox/clang-head/lib/clang/9.0.0 -I
/opt/wandbox/clang-head/include/c++/v1 -I /opt/wandbox/boost-sml/include -I
/opt/wandbox/boost-di/include -I /opt/wandbox/range-v3/include -I
/opt/wandbox/nlohmann-json/src -I /opt/wandbox/cmcstl2/include -I
/opt/wandbox/te/include -internal-isystem /usr/local/include -internal-isystem
/opt/wandbox/clang-head/lib/clang/9.0.0/include -internal-externc-isystem
/usr/include/x86_64-linux-gnu -internal-externc-isystem /include
-internal-externc-isystem /usr/include -fdeprecated-macro
-fdebug-compilation-dir /home/jail -ferror-limit 19 -fmessage-length 0
-fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option
-fcolor-diagnostics -fansi-escape-codes -faddrsig -o /tmp/prog-a3a167.o -x c++
prog.cc
1. parser at end of file
2. prog.cc:2:5: LLVM IR generation of declaration 'main'
3. prog.cc:2:5: Generating code for declaration 'main'
#0 0x01fe2294 PrintStackTraceSignalHandler(void*)
(/opt/wandbox/clang-head/bin/clang-9+0x1fe2294)
#1 0x01fe01e0 llvm::sys::RunSignalHandlers()
(/opt/wandbox/clang-head/bin/clang-9+0x1fe01e0)
#2 0x01fe2698 SignalHandler(int)
(/opt/wandbox/clang-head/bin/clang-9+0x1fe2698)
#3 0x7fce1652c390 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x11390)
#4 0x01b1cf4a llvm::FunctionType::get(llvm::Type*,
llvm::ArrayRef, bool)
(/opt/wandbox/clang-head/bin/clang-9+0x1b1cf4a)
#5 0x0232293f
clang::CodeGen::CodeGenTypes::GetFunctionType(clang::CodeGen::CGFunctionInfo
const&) (/opt/wandbox/clang-head/bin/clang-9+0x232293f)
#6 0x02386d4b
clang::CodeGen::CodeGenFunction::EmitCXXMemberOrOperatorMemberCallExpr(clang::CallExpr
const*, clang::CXXMethodDecl const*, clang::CodeGen::ReturnValueSlot, bool,
clang::NestedNameSpecifier*, bool, clang::Expr const*)
(/opt/wandbox/clang-head/bin/clang-9+0x2386d4b)
#7 0x023879f8
clang::CodeGen::CodeGenFunction::EmitCXXOperatorMemberCallExpr(clang::CXXOperatorCallExpr
const*, clang::CXXMethodDecl const*, clang::CodeGen::ReturnValueSlot)
(/opt/wandbox/clang-head/bin/clang-9+0x23879f8)
#8 0x02378764
clang::CodeGen::CodeGenFunction::EmitCallExpr(clang::CallExpr const*,
clang::CodeGen::ReturnValueSlot)
(/opt/wandbox/clang-head/bin/clang-9+0x2378764)
#9 0x023a8344 (anonymous
namespace)::ScalarExprEmitter::VisitCallExpr(clang::CallExpr const*)
(/opt/wandbox/clang-head/bin/clang-9+0x23a8344)
#10 0x023a2960 clang::StmtVisitorBase::Visit(clang::Stmt*)
(/opt/wandbox/clang-head/bin/clang-9+0x23a2960)
#11 0x02396b12
clang::CodeGen::CodeGenFunction::EmitScalarExpr(clang::Expr const*, bool)
(/opt/wandbox/clang-head/bin/clang-9+0x2396b12)
#12 0x0235f553 clang::CodeGen::CodeGenFunction::EmitAnyExpr(clang::Expr
const*, clang::CodeGen::AggValueSlot, bool)
(/opt/wandbox/clang-head/bin/clang-9+0x235f553)
#13 0x0235f4a9
clang::CodeGen::CodeGenFunction::EmitIgnoredExpr(clang::Expr const*)
(/opt/wandbox/clang-head/bin/clang-9+0x235f4a9)
#14 0x021b2587 clang::CodeGen::CodeGenFunction::EmitStm
[llvm-bugs] [Bug 42586] New: ICE when compiling with -fopenmp and Catch2 unit test suite
https://bugs.llvm.org/show_bug.cgi?id=42586
Bug ID: 42586
Summary: ICE when compiling with -fopenmp and Catch2 unit test
suite
Product: clang
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++17
Assignee: unassignedclangb...@nondot.org
Reporter: ldalessan...@gmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
Created attachment 22230
--> https://bugs.llvm.org/attachment.cgi?id=22230&action=edit
reduced test case
Lukes-MacBook:test ldalessa$ clang++ --version
Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Target: x86_64-apple-darwin18.6.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
Lukes-MacBook:test ldalessa$ clang++ --version
Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Target: x86_64-apple-darwin18.6.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
Lukes-MacBook:test ldalessa$ cat test.cpp
#include
TEST_CASE ("Test", "") {
auto t0 = std::make_tuple();
REQUIRE (std::tuple_size_v == 0);
}
Lukes-MacBook:test ldalessa$ clang++ -Xclang -fopenmp -std=c++17 -save-temps -o
test.o -c test.cpp
clang: error: unable to execute command: Illegal instruction: 4
clang: error: clang frontend command failed due to signal (use -v to see
invocation)
Apple LLVM version 10.0.1 (clang-1001.0.46.4)
Target: x86_64-apple-darwin18.6.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
clang: note: diagnostic msg: PLEASE submit a bug report to
http://developer.apple.com/bugreporter/ and include the crash backtrace,
preprocessed source, and associated run script.
clang: note: diagnostic msg:
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang: note: diagnostic msg:
/var/folders/nm/j3bknc2n2t7f8llmt1m8j468gn/T/test-36c4ea.cpp
clang: note: diagnostic msg:
/var/folders/nm/j3bknc2n2t7f8llmt1m8j468gn/T/test-36c4ea.sh
clang: note: diagnostic msg: Crash backtrace is located in
clang: note: diagnostic msg:
/Users/ldalessa/Library/Logs/DiagnosticReports/clang__.crash
clang: note: diagnostic msg: (choose the .crash file that corresponds to your
crash)
clang: 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] [Bug 42585] New: SROA assert fails VTy == CandidateTys[0] && "Different vector types with the same element type!
https://bugs.llvm.org/show_bug.cgi?id=42585
Bug ID: 42585
Summary: SROA assert fails VTy == CandidateTys[0] && "Different
vector types with the same element type!
Product: new-bugs
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: felipe.de.azevedo.piove...@intel.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
The following IR causes SROA to assert a failure. Verified this on a trunk
build with asserts on.
opt test.ll -sroa
target datalayout =
"e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-n8:16:32:64"
define <4 x i1> @vector_bitcast() {
; CHECK-LABEL: @vector_bitcast
%a = alloca <3 x i1>
store <3 x i1> , <3 x i1>* %a
%cast = bitcast <3 x i1>* %a to <4 x i1>*
%vec = load <4 x i1>, <4 x i1>* %cast
ret <4 x i1> %vec
}
--
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 42584] New: clang++ -opt-bisect-limit SIGSEGV with Emulated TLS
https://bugs.llvm.org/show_bug.cgi?id=42584 Bug ID: 42584 Summary: clang++ -opt-bisect-limit SIGSEGV with Emulated TLS Product: new-bugs Version: 8.0 Hardware: PC OS: OpenBSD Status: NEW Severity: normal Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: bsdk...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org Summary: On OpenBSD/i386 -current with clang++ 8.0.0 I hit a SIGSEGV in clang++ while using -opt-bisect-limit. I believe this is due to llvm/lib/CodeGen/LowerEmuTLS.cpp incorrectly skipping this pass when it is required on platforms that use Emulated TLS like OpenBSD. Removing the following two lines: if (skipModule(M)) return false; in LowerEmuTLS::runOnModule(Module &M) corrects the segfault. Details: BISECT: NOT running pass (17334) Machine Copy Propagation Pass on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17335) Post RA top-down list latency scheduler on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17336) Branch Probability Basic Block Placement on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17337) ReachingDefAnalysis on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17338) X86 Execution Dependency Fix on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17339) BreakFalseDeps on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17340) X86 Byte/Word Instruction Fixup on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17341) X86 Atom pad short functions on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17342) X86 LEA Fixup on function (_ZN6Thread25set_current_resource_markEP12ResourceMark) BISECT: NOT running pass (17343) X86 DAG->DAG Instruction Selection on function (_ZN6Thread15current_or_nullEv) clang++: error: unable to execute command: Segmentation fault (core dumped) clang++: error: clang frontend command failed due to signal (use -v to see invocation) OpenBSD clang version 8.0.0 (tags/RELEASE_800/final) (based on LLVM 8.0.0) Target: i386-unknown-openbsd6.5 Thread model: posix InstalledDir: /usr/bin clang++: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associa ted run script. clang++: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: clang++: note: diagnostic msg: /tmp/stubRoutines-304a42.cpp clang++: note: diagnostic msg: /tmp/stubRoutines-304a42.sh clang++: note: diagnostic msg: (gdb) bt #0 llvm::SelectionDAG::getGlobalAddress (this=0x3f499400, GV=0x0, DL=..., VT=..., Offset=0, isTargetGA=, TargetFlags=) at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/CodeGen/SelectionDAG/SelectionDAG.cpp:1339 #1 0x01b98e36 in LowerToTLSEmulatedModel () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/CodeGen/SelectionDAG/TargetLowering.cpp:5231 #2 0x01cee0e9 in LowerGlobalTLSAddress () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/X86/X86ISelLowering.cpp:17054 #3 0x01d180fc in LowerOperation () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/X86/X86ISelLowering.cpp:26204 #4 0x01ec7895 in LegalizeOp () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/CodeGen/SelectionDAG/LegalizeDAG.cpp:1213 #5 0x01ec71c6 in Legalize () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/CodeGen/SelectionDAG/LegalizeDAG.cpp:4578 #6 0x01b2c080 in CodeGenAndEmitDAG () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:864 #7 0x01b2acfc in SelectAllBasicBlocks () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:1784 #8 0x01b280fd in runOnMachineFunction () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/CodeGen/SelectionDAG/SelectionDAGISel.cpp:471 #9 0x00ebb2a6 in runOnMachineFunction () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:185 #10 0x011047d7 in runOnFunction () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/CodeGen/MachineFunctionPass.cpp:74 #11 0x010ed420 in runOnFunction () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/IR/LegacyPassManager.cpp:1644 #12 0x010ed6b9 in runOnModule () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/IR/LegacyPassManager.cpp:1679 #13 0x010eda8d in runOnModule () at /usr/src/gnu/usr.bin/clang/libLLVM/../../../llvm/lib/IR/LegacyPassManager.cpp:1744 #14 run () at /usr/src/gnu/usr
[llvm-bugs] [Bug 42572] std::ofstream silently fails to write files when they can't be created
https://bugs.llvm.org/show_bug.cgi?id=42572 Marshall Clow (home) changed: What|Removed |Added Resolution|--- |INVALID Status|CONFIRMED |RESOLVED --- Comment #6 from Marshall Clow (home) --- Not a libc++ bug. -- 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 42583] "-cc1as" doesn't supports non absolute preprocessor expressions
https://bugs.llvm.org/show_bug.cgi?id=42583 Tim Northover changed: What|Removed |Added Status|NEW |RESOLVED CC||t.p.northo...@gmail.com Resolution|--- |INVALID --- Comment #1 from Tim Northover --- Clang doesn't run the preprocessor on files named *.s. You should rename it to *.S (capital letter) and then the snippet works for me. -- 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 42583] New: "-cc1as" doesn't supports non absolute preprocessor expressions
https://bugs.llvm.org/show_bug.cgi?id=42583 Bug ID: 42583 Summary: "-cc1as" doesn't supports non absolute preprocessor expressions Product: clang Version: 8.0 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P Component: Driver Assignee: unassignedclangb...@nondot.org Reporter: qwertyt...@gmail.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk It is not possible to compile following assembly source code: ``` #define OPERATION_ADD 0 #define OPERATION_SUB 1 .macro EXECUTE operation .if \operation == OPERATION_ADD add x0, x1, #1 .endif .if \operation == OPERATION_SUB sub x0, x1, #1 .endif .endm EXECUTE OPERATION_ADD ``` Clang reports following error: ``` /opt/toolchains/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04/bin/aarch64-funnyos-gnueabi-clang -c preprocessor_arm.s :2:5: error: expected absolute expression .if OPERATION_SUB == OPERATION_ADD ^ preprocessor_arm.s:16:1: note: while in macro instantiation EXECUTE OPERATION_SUB ^ :6:5: error: expected absolute expression .if OPERATION_SUB == OPERATION_SUB ^ preprocessor_arm.s:16:1: note: while in macro instantiation EXECUTE OPERATION_SUB ^ ``` P.S. aarch64-funnyos-gnueabi-clang is a symlink to clang. P.S. As I frequently wrote before: "It compiles by GCC". P.P.S. LLVM is a future :) -- 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 38549] After r326641/r326813, error: duplicate symbol 'pdb_search_init' in version script
https://bugs.llvm.org/show_bug.cgi?id=38549 Fangrui Song changed: What|Removed |Added CC||i...@maskray.me Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Fangrui Song --- There was an error because `assignWildcardVersion(ver, VER_NDX_LOCAL);` was processed before `assignExactVersion(ver, v.id, v.name);`. assignExactVersion issued an error if the symbol version was assigned before. Fixed by D64550/r365760. The change shall be included by lld 9.0.0 -- 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 42582] New: Assembly instructions "adrl, cpy, vmrs, vmsr" doesn't supported by Clang
https://bugs.llvm.org/show_bug.cgi?id=42582
Bug ID: 42582
Summary: Assembly instructions "adrl, cpy, vmrs, vmsr" doesn't
supported by Clang
Product: clang
Version: 8.0
Hardware: Other
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: qwertyt...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
Created attachment 4
--> https://bugs.llvm.org/attachment.cgi?id=4&action=edit
Test to reproduce situation
Assembly instructions "adrl, cpy, vmrs, vmsr" don't supported by Clang.
At the same time, they are supported by GCC.
Environment information:
OS:Ubuntu 16.04.5 LTS
GCC: arm-linux-gnueabihf-gcc (Linaro GCC 6.2-2016.11) 6.2.1 20161016
CLANG: clang version 8.0.0 (tags/RELEASE_800/final)
Usecase is attached to this report. Also it is duplicated below in this text:
adrl_cpy_vmrs_vmsr.s
```
add:
adrl r0, add
cpy r0, r1
VMRS r2,FPEXC
VMSR FPEXC,r2
```
adrl_cpy_vmrs_vmsr.sh
```
#!/bin/bash
COMPILER_GCC=/opt/toolchains/aarch32/bin/arm-linux-gnueabihf-gcc
COMPILER_CLANG=opt/clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04/bin/arm-funnyos-gnueabi-clang
i=adrl_cpy_vmrs_vmsr;
echo "=="
echo "Building by GCC";
echo "=="
${COMPILER_GCC} -c $i.s;
RESULT=$?
echo "--"
echo "Build result: $RESULT";
echo "--"
echo "";
echo "";
echo "=="
echo "Building by CLANG";
echo "=="
${COMPILER_CLANG} -c $i.s;
RESULT=$?
echo "--"
echo "Build result: $RESULT";
echo "--"
echo "";
echo "";
```
Result of "adrl_cpy_vmrs_vmsr.sh" execution:
```
$ ./adrl_cpy_vmrs_vmsr.sh
==
Building by GCC
==
--
Build result: 0
--
==
Building by CLANG
==
adrl_cpy_vmrs_vmsr.s:2:1: error: invalid instruction, did you mean: adr?
adrl r0, add
^
adrl_cpy_vmrs_vmsr.s:3:1: error: invalid instruction, did you mean: cdp, cmp,
cps?
cpy r0, r1
^
adrl_cpy_vmrs_vmsr.s:4:1: error: instruction requires: VFP2
VMRS r2,FPEXC
^
adrl_cpy_vmrs_vmsr.s:5:1: error: instruction requires: VFP2
VMSR FPEXC,r2
^
--
Build result: 1
--
```
--
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 42581] New: clang crashed during compilation - template recursive constexpr function
https://bugs.llvm.org/show_bug.cgi?id=42581
Bug ID: 42581
Summary: clang crashed during compilation - template recursive
constexpr function
Product: clang
Version: 8.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++14
Assignee: unassignedclangb...@nondot.org
Reporter: vukki.starb...@gmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
Created attachment 3
--> https://bugs.llvm.org/attachment.cgi?id=3&action=edit
source,full backtrace and other data
clang crashed during compilation - template recursive constexpr function
full backtrace and other data are in the attachment.
source:
template constexpr int f()
{
return n<=1 ? 1: (n*f());
}
template
struct cti
{
};
int main(int argc,char * argv[])
{
cti()> l;
return 0;
}
backtrace's end:
#251 0x7f355c6df876 (/usr/bin/../lib64/../lib64/libclangSema.so.8+0x61f876)
#252 0x7f355c6cd42a clang::Sema::SubstStmt(clang::Stmt*,
clang::MultiLevelTemplateArgumentList const&)
(/usr/bin/../lib64/../lib64/libclangSema.so.8+0x60d42a)
#253 0x7f355c6fd106
clang::Sema::InstantiateFunctionDefinition(clang::SourceLocation,
clang::FunctionDecl*, bool, bool, bool)
(/usr/bin/../lib64/../lib64/libclangSema.so.8+0x63d106)
#254 0x7f355c4400f3
clang::Sema::MarkFunctionReferenced(clang::SourceLocation,
clang::FunctionDecl*, bool)
(/usr/bin/../lib64/../lib64/libclangSema.so.8+0x3800f3)
#255 0x7f355c4434ee (/usr/bin/../lib64/../lib64/libclangSema.so.8+0x3834ee)
clang-8.0: error: unable to execute command: Segmentation fault (core dumped)
clang-8.0: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 8.0.0 (tags/RELEASE_800/final 356365)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang-8.0: note: diagnostic msg: PLEASE submit a bug report to
https://bugs.llvm.org/ and include the crash backtrace, preprocessed source,
and associated run script.
--
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 42580] New: missed optimization leading to compiletime assert with address sanitizer
https://bugs.llvm.org/show_bug.cgi?id=42580
Bug ID: 42580
Summary: missed optimization leading to compiletime assert with
address sanitizer
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: a...@linaro.org
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
The current clang-9 prerelease causes one file in the linux kernel to get fail
compilation with an assertion triggering when building with
-sanitize=kernel-address:
void __iwl_err(char *, ...);
int a;
void iwl_fw_dbg_apply_point() {
const char b[] = "WRT ext=%d. Invalid apply point %d for %s\n";
if (a) {
void __compiletime_assert_2790(void);
if (b[sizeof(b) - 2] != '\n')
__compiletime_assert_2790();
}
__iwl_err(0, b);
}
$ clang-9 -O2 -fsanitize=kernel-address -S dbg.i -o-| grep compiletime
callq __compiletime_assert_2790
both clang-8 and gcc-8 pass the assertion here.
See also https://godbolt.org/z/cPrkv4
--
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 15623 in oss-fuzz: llvm: Build failure
Comment #3 on issue 15623 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15623#c3 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-ca0208cb-cb6f-40ed-8946-7a4b170d6fea.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 42579] New: Build is failing while compiling using clang++ language flags -fprofile-instr-generate -fcoverage-mapping
https://bugs.llvm.org/show_bug.cgi?id=42579
Bug ID: 42579
Summary: Build is failing while compiling using clang++
language flags -fprofile-instr-generate
-fcoverage-mapping
Product: tools
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: release blocker
Priority: P
Component: llvm-bcanalyzer
Assignee: unassignedb...@nondot.org
Reporter: agarwala.sou...@gmail.com
CC: llvm-bugs@lists.llvm.org
=
ERROR SCENARIO
clang --version
==
Chromium OS 9.0_pre353983_p20190325-r19 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm-project
de7a0a152648d1a74cf4319920b1848aa00d1ca3) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
My test code is –cat test.cc
===
#include
using namespace std;
int main()
{
cout << "Hello World\n";
return 0;
}
Compiler the code using the below command
==
clang++ -Wall -fprofile-instr-generate -fcoverage-mapping test.cc -o test
In the above command both the flags are required because I want to generate
code coverage report.
-fprofile-instr-generate -fcoverage-mapping
Below is the ERROR Message
===
fatal error: error in backend: Cannot select: intrinsic
%llvm.instrprof.increment
clang-9: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
Chromium OS 9.0_pre353983_p20190325-r19 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm-project
de7a0a152648d1a74cf4319920b1848aa00d1ca3) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang-9: 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-9: note: diagnostic msg:
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-9: note: diagnostic msg: /tmp/test-2a3ff5.cpp
clang-9: note: diagnostic msg: /tmp/test-2a3ff5.sh
clang-9: note: diagnostic msg:
=
WORKING SCENARIO
Another system where clang++ version is shown below
clang++ --version
Chromium OS 9.0_pre353983_p20190325-r1 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/clang.git
171531e31716e2db2c372cf8b57220ddf9e721d8)
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm.git
5077597e0d5b86d9f9c27286d8b28f8b3645a74c) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Source code and compilation step is same. Build successfully and object is
created.
--
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 42578] New: Build is failing while compiling using clang++ language flags -fprofile-instr-generate -fcoverage-mapping
https://bugs.llvm.org/show_bug.cgi?id=42578
Bug ID: 42578
Summary: Build is failing while compiling using clang++
language flags -fprofile-instr-generate
-fcoverage-mapping
Product: Test Suite
Version: trunk
Hardware: PC
OS: other
Status: NEW
Severity: release blocker
Priority: P
Component: Programs Tests
Assignee: unassignedb...@nondot.org
Reporter: agarwala.sou...@gmail.com
CC: llvm-bugs@lists.llvm.org
=
ERROR SCENARIO
clang --version
==
Chromium OS 9.0_pre353983_p20190325-r19 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm-project
de7a0a152648d1a74cf4319920b1848aa00d1ca3) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
My test code is –cat test.cc
===
#include
using namespace std;
int main()
{
cout << "Hello World\n";
return 0;
}
Compiler the code using the below command
==
clang++ -Wall -fprofile-instr-generate -fcoverage-mapping test.cc -o test
In the above command both the flags are required because I want to generate
code coverage report.
-fprofile-instr-generate -fcoverage-mapping
Below is the ERROR Message
===
fatal error: error in backend: Cannot select: intrinsic
%llvm.instrprof.increment
clang-9: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
Chromium OS 9.0_pre353983_p20190325-r19 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm-project
de7a0a152648d1a74cf4319920b1848aa00d1ca3) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang-9: 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-9: note: diagnostic msg:
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-9: note: diagnostic msg: /tmp/test-2a3ff5.cpp
clang-9: note: diagnostic msg: /tmp/test-2a3ff5.sh
clang-9: note: diagnostic msg:
=
WORKING SCENARIO
Another system where clang++ version is shown below
clang++ --version
Chromium OS 9.0_pre353983_p20190325-r1 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/clang.git
171531e31716e2db2c372cf8b57220ddf9e721d8)
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm.git
5077597e0d5b86d9f9c27286d8b28f8b3645a74c) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Source code and compilation step is same. Build successfully and object is
created.
--
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 42577] New: Build is failing while compiling using clang++ language with flags -fprofile-instr-generate -fcoverage-mapping
https://bugs.llvm.org/show_bug.cgi?id=42577
Bug ID: 42577
Summary: Build is failing while compiling using clang++
language with flags -fprofile-instr-generate
-fcoverage-mapping
Product: clang
Version: unspecified
Hardware: Other
OS: other
Status: NEW
Severity: release blocker
Priority: P
Component: C++14
Assignee: unassignedclangb...@nondot.org
Reporter: agarwala.sou...@gmail.com
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
=
ERROR SCENARIO
clang --version
==
Chromium OS 9.0_pre353983_p20190325-r19 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm-project
de7a0a152648d1a74cf4319920b1848aa00d1ca3) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
My test code is –cat test.cc
===
#include
using namespace std;
int main()
{
cout << "Hello World\n";
return 0;
}
Compiler the code using the below command
==
clang++ -Wall -fprofile-instr-generate -fcoverage-mapping test.cc -o test
In the above command both the flags are required because I want to generate
code coverage report.
-fprofile-instr-generate -fcoverage-mapping
Below is the ERROR Message
===
fatal error: error in backend: Cannot select: intrinsic
%llvm.instrprof.increment
clang-9: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
Chromium OS 9.0_pre353983_p20190325-r19 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm-project
de7a0a152648d1a74cf4319920b1848aa00d1ca3) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
clang-9: 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-9: note: diagnostic msg:
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-9: note: diagnostic msg: /tmp/test-2a3ff5.cpp
clang-9: note: diagnostic msg: /tmp/test-2a3ff5.sh
clang-9: note: diagnostic msg:
=
WORKING SCENARIO
Another system where clang++ version is shown below
clang++ --version
Chromium OS 9.0_pre353983_p20190325-r1 clang version 9.0.0
(/var/cache/chromeos-cache/distfiles/host/egit-src/clang.git
171531e31716e2db2c372cf8b57220ddf9e721d8)
(/var/cache/chromeos-cache/distfiles/host/egit-src/llvm.git
5077597e0d5b86d9f9c27286d8b28f8b3645a74c) (based on LLVM 9.0.0svn)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin
Source code and compilation step is same. Build successfully and object is
created.
--
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 42576] New: aarch64: -march=armv8-a produces armv8.2 'bfc' instruction
https://bugs.llvm.org/show_bug.cgi?id=42576
Bug ID: 42576
Summary: aarch64: -march=armv8-a produces armv8.2 'bfc'
instruction
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C
Assignee: unassignedclangb...@nondot.org
Reporter: a...@linaro.org
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Building arm64 linux randconfig kernels, I came across this assembler error:
/tmp/sdma_v4_0-f95fd3.s: Assembler messages:
/tmp/sdma_v4_0-f95fd3.s:44: Error: selected processor does not support `bfc
w0,#1,#5'
I reduced the test case to
int a, b, c;
int __order_base_2() { return a > 1 ? __builtin_constant_p(a) ?: b : 0; }
int sdma_v4_0_rb_cntl(int p1) {
int d = c ?: __order_base_2();
p1 = (p1 & ~0x003EL) | (62 & (d << 1));
return p1;
}
$ clang-8 --prefix=/home/arnd/cross/x86_64/gcc-8.1.0-nolibc/aarch64-linux/bin/
-no-integrated-as -O2 sdma_v4_0.i --target=aarch64-linux -S -o-
-march=armv8.1-a
https://godbolt.org/z/8Gcjl9 shows the 'bfc' instruction being generated, but
not the error message as it is unable to call the external assembler correctly.
According to https://sourceware.org/ml/binutils/2015-11/msg00221.html, the
'bfc' instruction is only valid in armv8.2 or higher but llvm uses it for any
armv8 version.
--
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 15734 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::Expected::fatalUncheckedExpected
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-07-11 Type: Bug New issue 15734 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: Abrt in llvm::Expected::fatalUncheckedExpected https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15734 Detailed report: https://oss-fuzz.com/testcase?key=5692605972611072 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2 Fuzz target binary: llvm-isel-fuzzer--x86_64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: llvm::Expected::fatalUncheckedExpected llvm::BitstreamCursor::skipRecord llvm::getBitcodeFileContents Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201906260258:201906270304 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5692605972611072 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. -- 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 42575] New: CLANG_LINK_CLANG_DYLIB=ON does not work with LLVM_INSTALL_TOOLCHAIN_ONLY=ON
https://bugs.llvm.org/show_bug.cgi?id=42575 Bug ID: 42575 Summary: CLANG_LINK_CLANG_DYLIB=ON does not work with LLVM_INSTALL_TOOLCHAIN_ONLY=ON Product: clang Version: trunk Hardware: All OS: All Status: NEW Severity: normal Priority: P Component: libclang Assignee: unassignedclangb...@nondot.org Reporter: ahee...@gmail.com CC: kli...@google.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk If llvm + clang is built with CLANG_LINK_CLANG_DYLIB=ON, or LLVM_LINK_LLVM_DYLIB=ON (which sets CLANG_LINK_CLANG_DYLIB=ON) and LLVM_INSTALL_TOOLCHAIN_ONLY=ON at the same time, the resulting clang binary crashes with the error message: ``` clang: error while loading shared libraries: libclang_shared.so.9svn: cannot open shared object file: No such file or directory ``` This message is from Linux, but other platforms have similar messages. I haven't checked on Windows, but Mac has the same error. I think even with `LLVM_INSTALL_TOOLCHAIN_ONLY=ON`, libclang_shared should be installed in lib/ directory to make binaries 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
