[llvm-bugs] [Bug 41409] New: possible silent bad code generation with inline static data member in clang-cl
https://bugs.llvm.org/show_bug.cgi?id=41409
Bug ID: 41409
Summary: possible silent bad code generation with inline static
data member in clang-cl
Product: clang
Version: 8.0
Hardware: PC
OS: other
Status: NEW
Severity: release blocker
Priority: P
Component: C++'17
Assignee: unassignedclangb...@nondot.org
Reporter: powerch...@web.de
CC: blitzrak...@gmail.com, erik.pilking...@gmail.com,
llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk
// header.h
#include
struct A
{
A() { std::cout << "ctor " << this << std::endl; }
~A() { std::cout << "dtor " << this << std::endl; }
void f() { std::cout << "f " << this << std::endl; }
};
struct S
{
inline static A a; // C++17 inline variable, thus also a definition
};
-
// TU1.cpp
#include "header.h"
int main()
{
S::a.f();
}
-
// TU2.cpp
#include "header.h"
-
// TU3.cpp
#include "header.h"
-
// TU4.cpp
#include "header.h"
-
This program prints (with some random address):
ctor 010D4020
ctor 010D4020
ctor 010D4020
ctor 010D4020
f 010D4020
dtor 010D4020
dtor 010D4020
dtor 010D4020
dtor 010D4020
These are four initializations for the one and only object of A (in fact one
per TU) instead of exactly one (as C++17 demands).
The program should print:
ctor 010D4020
f 010D4020
dtor 010D4020
I first reported this bug for clang-cl 6 (bug 37903 and bug 38171).
MSVC had the same bug, but Microsoft has fixed it (at least in VS2019):
https://developercommunity.visualstudio.com/content/problem/261624/multiple-initializations-of-inline-static-data-mem.html
See also https://stackoverflow.com/q/50982390/8731417.
I wonder why this bug has not been fixed yet because to me it seems pretty
serious. Do I rate that wrong?
--
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 10250 in oss-fuzz: llvm: Build failure
Comment #46 on issue 10250 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10250#c46 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-b4425a49-555a-4d2d-b922-dd61217b3021.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] Issue 14038 in oss-fuzz: llvm: Build failure
Updates: Status: Verified Comment #1 on issue 14038 by ClusterFuzz-External: llvm: Build failure https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14038#c1 The latest build has succeeded, closing this issue. -- 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 40696] Break after return type ignored with certain template parameters
https://bugs.llvm.org/show_bug.cgi?id=40696 MyDeveloperDay changed: What|Removed |Added Status|CONFIRMED |RESOLVED Fixed By Commit(s)||rL357837 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 40850] Add clang-format C# language support
https://bugs.llvm.org/show_bug.cgi?id=40850 MyDeveloperDay changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12291 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in llvm::llvm_unreachable_internal
Comment #5 on issue 12291 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12291#c5 ClusterFuzz has detected this issue as fixed in range 201903270300:201904052014. Detailed report: https://oss-fuzz.com/testcase?key=5731677305831424 Project: llvm Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--aarch64-O2 Fuzz target binary: llvm-isel-fuzzer--aarch64-O2 Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Abrt Crash Address: 0x0001 Crash State: llvm::llvm_unreachable_internal llvm::isAArch64FrameOffsetLegal llvm::AArch64FrameLowering::determineCalleeSaves Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5731677305831424 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12291 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in llvm::llvm_unreachable_internal
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #6 on issue 12291 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-O2: Abrt in llvm::llvm_unreachable_internal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12291#c6 ClusterFuzz testcase 5731677305831424 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12949 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: isGuardAsWidenableBranch(Guard) && "Stopped being a guard after transform?"
Comment #3 on issue 12949 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: isGuardAsWidenableBranch(Guard) && "Stopped being a guard after transform?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12949#c3 ClusterFuzz has detected this issue as fixed in range 201903270300:201904052014. Detailed report: https://oss-fuzz.com/testcase?key=5655006718459904 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-loop_predication Fuzz target binary: llvm-opt-fuzzer--x86_64-loop_predication Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: isGuardAsWidenableBranch(Guard) && "Stopped being a guard after transform?" LoopPredication::runOnLoop llvm::LoopPredicationPass::run Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901220414:201902020421 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5655006718459904 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12949 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: isGuardAsWidenableBranch(Guard) && "Stopped being a guard after transform?"
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #4 on issue 12949 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-loop_predication: ASSERT: isGuardAsWidenableBranch(Guard) && "Stopped being a guard after transform?" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12949#c4 ClusterFuzz testcase 5655006718459904 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12897 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray
Comment #6 on issue 12897 by ClusterFuzz-External:
llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in
llvm::ms_demangle::Node**
llvm::ms_demangle::ArenaAllocator::allocArray
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12897#c6
ClusterFuzz has detected this issue as fixed in range
201903270300:201904052014.
Detailed report: https://oss-fuzz.com/testcase?key=5647811742269440
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer
Fuzz target binary: llvm-microsoft-demangle-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Heap-buffer-overflow WRITE {*}
Crash Address: 0x62130900
Crash State:
llvm::ms_demangle::Node**
llvm::ms_demangle::ArenaAllocator::allocArray
llvm::ms_demangle::Demangler::demangleArrayType
llvm::ms_demangle::Demangler::demangleType
Sanitizer: address (ASAN)
Recommended Security Severity: High
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410
Fixed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5647811742269440
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
instructions to reproduce this bug locally.
If you suspect that the result above is incorrect, try re-doing that job on
the test case report page.
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12897 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #7 on issue 12897 by ClusterFuzz-External: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12897#c7 ClusterFuzz testcase 5647811742269440 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37433] clang-format mistakes structured bindings for Objective-C
https://bugs.llvm.org/show_bug.cgi?id=37433 Reupen Shah changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Reupen Shah --- I can confirm that. Weren't you the one that fixed it? :) https://reviews.llvm.org/D59546 -- 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 41409] possible silent bad code generation with inline static data member in clang-cl
https://bugs.llvm.org/show_bug.cgi?id=41409 Tim Northover changed: What|Removed |Added CC||t.p.northo...@gmail.com Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Tim Northover --- I know it's frustrating when bugs don't get the attention you think they deserve, but creating intentional duplicates isn't the way to fix it. You might try getting people interested in other venues like llvm-dev or the IRC channel. *** This bug has been marked as a duplicate of bug 37903 *** -- 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 41410] New: Misleading error message 'this' was not captured for this lambda function
https://bugs.llvm.org/show_bug.cgi?id=41410
Bug ID: 41410
Summary: Misleading error message 'this' was not captured for
this lambda function
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: gabriel.aubut-luss...@outlook.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
The error message given when 'this' cannot be captured is misleading in the
sense that it points the user to the lambda that fails to capture 'this' rather
than raise questions about why it fails to do so.
The icc compiler does the best job of giving context with this error. MSVC also
displays a bit more information. Clang has the worst offender. GCC could use a
bit of improvement. Aiming for an error message that is closer to icc seems
like the ideal solution. The error message given by icc is the following:
error: this enclosing-function local variable cannot be referenced in this
lambda body because an enclosing lambda does not allow implicit captures
Godbolt : https://gcc.godbolt.org/z/rmefHT
Sample code for the issue:
struct S
{
void f() {
[]() {
[this]() {
}();
}();
}
};
int main()
{
S s;
s.f();
}
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41411] New: not enough memory
https://bugs.llvm.org/show_bug.cgi?id=41411 Bug ID: 41411 Summary: not enough memory Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: release blocker Priority: P Component: COFF Assignee: unassignedb...@nondot.org Reporter: stonedreamfor...@gmail.com CC: llvm-bugs@lists.llvm.org when i use llvm for windows link v8 static library with chrome/v8/samples/process.cc lld will be report this bug !!! My computer have 16g ddr4 memory vs2017 v15.9.11 LLVM-9.0.0-r357435-win32.exe -- 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 41412] New: AVX512 register allocator thrashing
https://bugs.llvm.org/show_bug.cgi?id=41412 Bug ID: 41412 Summary: AVX512 register allocator thrashing Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: sland...@gmail.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org The register allocator is thrashing registers when doing AVX512 loads with duff's device. https://zig.godbolt.org/z/a9wxiu It repeatedly "bumps" registers up one number. -- 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 14106 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: !AM.Disp && "Non-zero displacement is ignored with JT."
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 Proj-llvm Reported-2019-04-06 Type: Bug New issue 14106 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: !AM.Disp && "Non-zero displacement is ignored with JT." https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14106 Detailed report: https://oss-fuzz.com/testcase?key=5769329678745600 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: ASSERT Crash Address: Crash State: !AM.Disp && "Non-zero displacement is ignored with JT." X86DAGToDAGISel::getAddressOperands X86DAGToDAGISel::selectAddr Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903270300:201904052014 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5769329678745600 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41407] Constructor initializer list indented incorrectly
https://bugs.llvm.org/show_bug.cgi?id=41407 Owen Pan changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||rL357851 -- 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 39067] The keyword "try" in C++ function-try-blocks doesn't obey BraceWrapping settings
https://bugs.llvm.org/show_bug.cgi?id=39067 Owen Pan changed: What|Removed |Added Fixed By Commit(s)||rL343305 Resolution|--- |FIXED Status|NEW |RESOLVED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41413] New: clang-format incorrectly indents wrapped closing parenthesis
https://bugs.llvm.org/show_bug.cgi?id=41413
Bug ID: 41413
Summary: clang-format incorrectly indents wrapped closing
parenthesis
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: owenpi...@gmail.com
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
The wrapped closing parentheses below should not be but are indented:
Foo::Foo(
//
)
: foo(0) {}
int Foo::getter(
//
) const {
return foo;
}
--
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 41414] New: Cannot emit physreg copy instruction after r357703
https://bugs.llvm.org/show_bug.cgi?id=41414 Bug ID: 41414 Summary: Cannot emit physreg copy instruction after r357703 Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: natechancel...@gmail.com CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org, llvm-...@redking.me.uk, spatel+l...@rotateright.com After r357703, my bootstrap LLVM build fails with the following output: [4434/4446] Linking CXX executable bin/llvm-xray FAILED: bin/llvm-xray : && /mnt/build/llvm/stage1/bin/clang++ -O2 -march=native -mtune=native -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -w -fdiagnostics-color -ffunction-sections -fdata-sections -flto=thin -O3 -DNDEBUG -fuse-ld=lld -Wl,--color-diagnostics -flto=thin -Wl,--thinlto-cache-dir=/mnt/build/llvm/lto.cache -Wl,-allow-shlib-undefined -Wl,-O3 -Wl,--gc-sections tools/llvm-xray/CMakeFiles/llvm-xray.dir/func-id-helper.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/llvm-xray.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-account.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-color-helper.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-converter.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-extract.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-fdr-dump.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-graph-diff.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-graph.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-registry.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-stacks.cpp.o -o bin/llvm-xray -Wl,-rpath,"\$ORIGIN/../lib" lib/libLLVMARMCodeGen.a lib/libLLVMARMAsmParser.a lib/libLLVMARMAsmPrinter.a lib/libLLVMARMDesc.a lib/libLLVMARMDisassembler.a lib/libLLVMARMInfo.a lib/libLLVMARMUtils.a lib/libLLVMAArch64CodeGen.a lib/libLLVMAArch64AsmParser.a lib/libLLVMAArch64AsmPrinter.a lib/libLLVMAArch64Desc.a lib/libLLVMAArch64Disassembler.a lib/libLLVMAArch64Info.a lib/libLLVMAArch64Utils.a lib/libLLVMPowerPCCodeGen.a lib/libLLVMPowerPCAsmParser.a lib/libLLVMPowerPCAsmPrinter.a lib/libLLVMPowerPCDesc.a lib/libLLVMPowerPCDisassembler.a lib/libLLVMPowerPCInfo.a lib/libLLVMX86CodeGen.a lib/libLLVMX86AsmParser.a lib/libLLVMX86AsmPrinter.a lib/libLLVMX86Desc.a lib/libLLVMX86Disassembler.a lib/libLLVMX86Info.a lib/libLLVMX86Utils.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMObject.a lib/libLLVMSupport.a lib/libLLVMSymbolize.a lib/libLLVMXRay.a -lpthread lib/libLLVMARMDesc.a lib/libLLVMARMAsmPrinter.a lib/libLLVMARMInfo.a lib/libLLVMARMUtils.a lib/libLLVMAArch64Desc.a lib/libLLVMAArch64AsmPrinter.a lib/libLLVMAArch64Info.a lib/libLLVMAArch64Utils.a lib/libLLVMPowerPCAsmPrinter.a lib/libLLVMAsmPrinter.a lib/libLLVMGlobalISel.a lib/libLLVMSelectionDAG.a lib/libLLVMCodeGen.a lib/libLLVMScalarOpts.a lib/libLLVMAggressiveInstCombine.a lib/libLLVMInstCombine.a lib/libLLVMBitWriter.a lib/libLLVMTransformUtils.a lib/libLLVMTarget.a lib/libLLVMAnalysis.a lib/libLLVMProfileData.a lib/libLLVMX86AsmPrinter.a lib/libLLVMX86Utils.a lib/libLLVMMCDisassembler.a lib/libLLVMDebugInfoDWARF.a lib/libLLVMDebugInfoPDB.a lib/libLLVMObject.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMDebugInfoCodeView.a lib/libLLVMDebugInfoMSF.a lib/libLLVMBitReader.a lib/libLLVMCore.a lib/libLLVMBinaryFormat.a lib/libLLVMSupport.a -lz -lrt -ldl -lpthread -lm lib/libLLVMDemangle.a && : LLVM ERROR: Cannot emit physreg copy instruction clang-9: error: linker command failed with exit code 1 (use -v to see invocation) I went ahead and enabled assertions, which then fails as such: [4434/4446] Linking CXX executable bin/llvm-xray FAILED: bin/llvm-xray : && /mnt/build/llvm/stage1/bin/clang++ -O2 -march=native -mtune=native -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -w -fdiagnostics-color -ffunction-sections -fdata-sections -flto=thin -O3 -fuse-ld=lld -Wl,--color-diagnostics -flto=thin -Wl,--thinlto-cache-dir=/mnt/build/llvm/lto.cache -Wl,-allow-shlib-undefined -Wl,-O3 -Wl,--gc-sections tools/llvm-xray/CMakeFiles/llvm-xray.dir/func-id-helper.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/llvm-xray.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-account.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-color-helper.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-converter.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-extract.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-fdr-dump.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-graph-diff.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-graph.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-registry.cpp.o tools/llvm-xray/CMakeFiles/llvm-xray.dir/xray-stacks.cpp.o -o bin/llvm-xray -Wl,-rpath,"\$ORIGIN/../lib" lib/libLLVMA
