[llvm-bugs] [Bug 34192] New: [5.0] check-lldb-unit hangs with lldb-server running
https://bugs.llvm.org/show_bug.cgi?id=34192 Bug ID: 34192 Summary: [5.0] check-lldb-unit hangs with lldb-server running Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: hah...@hahnjo.de CC: llvm-bugs@lists.llvm.org As said in the title, check-lldb-unit hangs while a process 'lldb-server' is still running and consuming 100% CPU. If I run tools/lldb/unittests/tools/lldb-server/tests/LLDBServerTests manually, I get: [==] Running 1 test from 1 test case. [--] Global test environment set-up. [--] 1 test from ThreadsInJstopinfoTest [ RUN ] ThreadsInJstopinfoTest.TestStopReplyContainsThreadPcsLlgs lldb-server-local_buildConnection established. [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:171:: Send Packet: A214,0,2F746D702F6A683336363237362F636C75737465722D6870635F31373334342F6275696C642D352E302E307263322F66696E616C2F746F6F6C732F6C6C64622F756E697474657374732F746F6F6C732F6C6C64622D7365727665722F7468726561645F696E666572696F72,2,1,34 1502787553.110960007 < 1> read packet: + 1502787553.111004114 < 232> read packet: $A214,0,2F746D702F6A683336363237362F636C75737465722D6870635F31373334342F6275696C642D352E302E307263322F66696E616C2F746F6F6C732F6C6C64622F756E697474657374732F746F6F6C732F6C6C64622D7365727665722F7468726561645F696E666572696F72,2,1,34#1a 1502787553.111036062 < 1> send packet: + Launched '<...>/build-5.0.0rc2/final/tools/lldb/unittests/tools/lldb-server/thread_inferior' as process 31142... 1502787553.146780014 < 6> send packet: $OK#9a [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:174:: Read Packet: OK [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:171:: Send Packet: qLaunchSuccess 1502787553.146975040 < 1> read packet: + 1502787553.147003889 < 18> read packet: $qLaunchSuccess#a5 1502787553.147032976 < 1> send packet: + 1502787553.147064924 < 6> send packet: $OK#9a [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:174:: Read Packet: OK [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:171:: Send Packet: qProcessInfo 1502787553.147120953 < 1> read packet: + 1502787553.147138119 < 16> read packet: $qProcessInfo#dc 1502787553.147159100 < 1> send packet: + 1502787553.147363901 < 166> send packet: $pid:79a6;parent-pid:79a4;real-uid:651e;real-gid:651e;effective-uid:651e;effective-gid:651e;triple:7838365f36342d2d6c696e7578;ostype:linux;endian:little;ptrsize:8;#1f 1502787553.147422075 < 1> read packet: + [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:174:: Read Packet: pid:79a6;parent-pid:79a4;real-uid:651e;real-gid:651e;effective-uid:651e;effective-gid:651e;triple:7838365f36342d2d6c696e7578;ostype:linux;endian:little;ptrsize:8; [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:171:: Send Packet: QListThreadsInStopReply 1502787553.147484064 < 27> read packet: $QListThreadsInStopReply#21 1502787553.147500992 < 1> send packet: + 1502787553.147512913 < 6> send packet: $OK#9a 1502787553.147535086 < 1> read packet: + [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:174:: Read Packet: OK [ INFO ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:171:: Send Packet: vCont;c 1502787553.147579908 < 11> read packet: $vCont;c#a8 1502787553.147593975 < 1> send packet: + 1502787553.147814035 < 443> send packet: $O2f746d702f6a683336363237362f636c75737465722d6870635f31373334342f6275696c642d352e302e307263322f66696e616c2f746f6f6c732f6c6c64622f756e697474657374732f746f6f6c732f6c6c64622d7365727665722f7468726561645f696e666572696f723a206572726f72207768696c65206c6f6164696e6720736861726564206c69627261726965733a206c6962632b2b2e736f2e313a2063616e6e6f74206f70656e20736861726564206f626a6563742066696c653a204e6f20737563682066696c65206f72206469726563746f72790d0a#09 [ INFO ] 1502787553.147836924 < 1> read packet: + <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/TestClient.cpp:174:: Read Packet: O2f746d702f6a683336363237362f636c75737465722d6870635f31373334342f6275696c642d352e302e307263322f66696e616c2f746f6f6c732f6c6c64622f756e697474657374732f746f6f6c732f6c6c64622d7365727665722f7468726561645f696e666572696f723a206572726f72207768696c65206c6f6164696e6720736861726564206c69627261726965733a206c6962632b2b2e736f2e313a2063616e6e6f74206f70656e20736861726564206f626a6563742066696c653a204e6f20737563682066696c65206f72206469726563746f72790d0a 1502787553.147871971 < 7> send packet: $W7f#f4 [ ERROR ] <...>/src-5.0.0rc2/tools/lldb/unittests/tools/lldb-server/tests/Te
[llvm-bugs] [Bug 34193] New: False negative in following pointer for core.NullDereference
https://bugs.llvm.org/show_bug.cgi?id=34193
Bug ID: 34193
Summary: False negative in following pointer for
core.NullDereference
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: kreme...@apple.com
Reporter: whisper...@gmail.com
CC: llvm-bugs@lists.llvm.org
Consider the following code:
int* a(){ return nullptr; }
int main()
{
int* ptr = a();
intx = *ptr;
return x;
}
While this is clearly a null dereference, ClangSA does not seem to properly
follow this pointer in the analyzer, or some inner heuristics swallow this
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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 33922] [OpenMP 5.0] New ident_t flags for __kmpc_for_static_init()
https://bugs.llvm.org/show_bug.cgi?id=33922 Alexey Bataev changed: What|Removed |Added 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34194] New: LLDB fails to evaluate expressions which include string literals when linked against libLLVM.so
https://bugs.llvm.org/show_bug.cgi?id=34194
Bug ID: 34194
Summary: LLDB fails to evaluate expressions which include
string literals when linked against libLLVM.so
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-...@lists.llvm.org
Reporter: tsche...@redhat.com
CC: llvm-bugs@lists.llvm.org
Created attachment 18986
--> https://bugs.llvm.org/attachment.cgi?id=18986&action=edit
Shell script to reproduce the bug.
Description of problem:
LLDB fails to evaluate expressions which include string literals if built with
-DLLVM_LINK_LLVM_DYLIB=ON.
Version-Release number of selected component (if applicable):
Reproduces with trunk (r310911)
How reproducible:
100%
Steps to Reproduce:
1.
$ cat >test.c
#include
int main(void) {
return 0;
}
2. gcc -g test.c -o test
3.
$ lldb ./test
(lldb) target create "./test"
Current executable set to './test' (x86_64).
(lldb) b main
Breakpoint 1: where = test`main + 4 at test.c:4, address = 0x004004f1
(lldb) r
Process 196442 launched: './test' (x86_64)
Process 196442 stopped
* thread #1, name = 'test', stop reason = breakpoint 1.1
frame #0: test`main at test.c:4
1#include
2
3int main(void) {
-> 4 return 0;
5}
(lldb) expr "hello"
error: Couldn't apply expression side effects : Couldn't dematerialize a result
variable: couldn't read its memory
(lldb) expr printf("hello")
error: Execution was interrupted, reason: signal SIGSEGV: invalid address
(fault address: 0x7fdbfac1e000).
The process has been returned to the state before expression evaluation.
Actual results:
(lldb) expr "hello"
error: Couldn't apply expression side effects : Couldn't dematerialize a result
variable: couldn't read its memory
(lldb) expr printf("hello")
error: Execution was interrupted, reason: signal SIGSEGV: invalid address
(fault address: 0x7fdbfac1e000).
The process has been returned to the state before expression evaluation.
Expected results:
(lldb) expr "hello"
(const char [6]) $0 = "hello"
(lldb) expr printf("hello")
Additional info:
Works fine in the static build (see expected results) but doesn't work with
-DLLVM_LINK_LLVM_DYLIB=ON active.
Attached is a shell script which builds trunk LLVM/Clang/LLDB separately and
with -DLLVM_LINK_LLVM_DYLIB=ON. Once the build is complete it also runs the
above test case.
I have spent a significant amount of time to debug this already and it looks
like some sort of memory corruption that happens early on during the evaluation
of the 'expr "hello"' command. E.g. in a release build of Clang/LLVM/LLDB and
with "log enable lldb all" you can see that the generated LLVM IR for the
expression is slightly different in the static and dynamic build. These
differences are not visible in the debug build but it seems that there's
definitely some memory corruption going on somewhere.
Also tried to run this with AddressSanitizer but didn't get any suspicious
reports.
Reproduces at least with GCC 4.8, GCC 6.3.1 and Clang 4.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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 32021] Clang-CL can not compile TraceLoggingProvider.h
https://bugs.llvm.org/show_bug.cgi?id=32021 David Majnemer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from David Majnemer --- *** This bug has been marked as a duplicate of bug 30932 *** -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34196] New: c++14 cause worse codegen than c++1z.
https://bugs.llvm.org/show_bug.cgi?id=34196
Bug ID: 34196
Summary: c++14 cause worse codegen than c++1z.
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: denis.yaroshevs...@gmail.com
CC: dgre...@apple.com, llvm-bugs@lists.llvm.org
Created attachment 18988
--> https://bugs.llvm.org/attachment.cgi?id=18988&action=edit
code
Hi.
I was playing with variant implementation and found out that c++1z option
produces a better code than with c++14. Might be worth looking into.
Unfortunately, links to goldbolt currently do not work, so I attach code as
file.
It's not exactly an easy read so quick idea:
for each possible combination of parameters, I instantiate a function. All of
this functions are written in one n-dimentional array, where each dimension
corresponds to an element.
So sum of two variants should be equivalent to:
int sum(const variant& x, const variant& y) {
using f_type = ...
static const f_type vtable = {
{
[](decltype(x) x, decltype(y) y) -> int {
return get<0>(x) + get<0>(y); },
[](decltype(x) x, decltype(y) y) -> int {
return get<0>(x) + get<1>(y); },
},
{
[](decltype(x) x, decltype(y) y) -> int {
return get<1>(x) + get<0>(y); },
[](decltype(x) x, decltype(y) y) -> int {
return get<1>(x) + get<1>(y); },
}
};
return vtable[x.idx][y.idx](x, y);
}
Compiling with c++1z generates 2 times less instructions than with c++14. This
does not seem right.
Compilation options: -Werror -Wall --std=c++1z -O3 -fno-exceptions -DNDEBUG
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34190] Core dump when printing error with invalid range-based for loop
https://bugs.llvm.org/show_bug.cgi?id=34190 Richard Smith changed: What|Removed |Added CC||richard-l...@metafoo.co.uk Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Richard Smith --- According to gcc.godbolt.org, this was fixed between Clang 3.8 and 3.9. Thanks for filing, but we're not issuing patch releases for 3.8 any more so there's not really anything we can do about this other than suggesting you upgrade to a more recent version of Clang. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 33082] assert failure due to pack expansion of variadic generic lambda
https://bugs.llvm.org/show_bug.cgi?id=33082 Richard Smith changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Richard Smith --- Fixed in r310946. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34197] New: x86: llc crashes when build a program
https://bugs.llvm.org/show_bug.cgi?id=34197 Bug ID: 34197 Summary: x86: llc crashes when build a program Product: new-bugs Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: yunl...@chromium.org CC: llvm-bugs@lists.llvm.org Created attachment 18989 --> https://bugs.llvm.org/attachment.cgi?id=18989&action=edit reproduce case generated by bugpoint. llc w.ll Can't get register for value! UNREACHABLE executed at /lib/CodeGen/SelectionDAG/SelectionDAGBuilder.cpp:1246! #0 0x7fbb076d7a8f llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0x8a7a8f) #1 0x7fbb076d7df6 (/usr/bin/../lib64/libLLVM-6.0svn.so+0x8a7df6) #2 0x7fbb067add70 (/lib64/libc.so.6+0x33d70) #3 0x7fbb067adcf2 gsignal (/lib64/libc.so.6+0x33cf2) #4 0x7fbb067afa2a abort (/lib64/libc.so.6+0x35a2a) #5 0x7fbb0766e8bb (/usr/bin/../lib64/libLLVM-6.0svn.so+0x83e8bb) #6 0x7fbb07cc56e7 llvm::SelectionDAGBuilder::getValueImpl(llvm::Value const*) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xe956e7) #7 0x7fbb07cc453f llvm::SelectionDAGBuilder::getValue(llvm::Value const*) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xe9453f) #8 0x7fbb07cd9d06 llvm::SelectionDAGBuilder::visitTargetIntrinsic(llvm::CallInst const&, unsigned int) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xea9d06) #9 0x7fbb07cdb7b7 llvm::SelectionDAGBuilder::visitIntrinsicCall(llvm::CallInst const&, unsigned int) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xeab7b7) #10 0x7fbb07cbeb70 llvm::SelectionDAGBuilder::visitCall(llvm::CallInst const&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xe8eb70) #11 0x7fbb07cb3916 llvm::SelectionDAGBuilder::visit(llvm::Instruction const&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xe83916) #12 0x7fbb07d477d1 llvm::SelectionDAGISel::SelectBasicBlock(llvm::ilist_iterator, false, true>, llvm::ilist_iterator, false, true>, bool&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xf177d1) #13 0x7fbb07d460ca llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xf160ca) #14 0x7fbb07d427e1 llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xf127e1) #15 0x7fbb09290851 (/usr/bin/../lib64/libLLVM-6.0svn.so+0x2460851) #16 0x7fbb0799bf94 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0xb6bf94) #17 0x7fbb077ece3f llvm::FPPassManager::runOnFunction(llvm::Function&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0x9bce3f) #18 0x7fbb077ed0c3 llvm::FPPassManager::runOnModule(llvm::Module&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0x9bd0c3) #19 0x7fbb077ed5b1 llvm::legacy::PassManagerImpl::run(llvm::Module&) (/usr/bin/../lib64/libLLVM-6.0svn.so+0x9bd5b1) #20 0x00418c66 (llc+0x418c66) #21 0x0041650b (llc+0x41650b) #22 0x7fbb0679a730 __libc_start_main (/lib64/libc.so.6+0x20730) #23 0x00410c29 (llc+0x410c29) Stack dump: 0. Program arguments: llc w.ll 1. Running pass 'Function Pass Manager' on module 'w.ll'. 2. Running pass 'X86 DAG->DAG Instruction Selection' on function '@__cxa_call_unexpected' Aborted (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 28820] Compile gets 10x slower (from 40s to 7m40s) due to using -g (on compiles with -fno-execptions)
https://bugs.llvm.org/show_bug.cgi?id=28820 Jonas Devlieghere changed: What|Removed |Added Status|NEW |RESOLVED CC||jo...@devlieghere.com Resolution|--- |FIXED --- Comment #10 from Jonas Devlieghere --- This issue no longer occurs on the current trunk: time bin/clang++ -arch x86_64 -O2 -isysroot $(xcrun -show-sdk-path) -std=c++11 -c foo_small.cc -g -fno-exceptions 10.26 real10.01 user 0.21 sys time bin/clang++ -arch x86_64 -O2 -isysroot $(xcrun -show-sdk-path) -std=c++11 -c foo_small.cc -fno-exceptions 4.72 real 4.53 user 0.13 sys -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 32021] Clang-CL can not compile TraceLoggingProvider.h
https://bugs.llvm.org/show_bug.cgi?id=32021 Reid Kleckner changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REOPENED Depends on||30932 --- Comment #4 from Reid Kleckner --- The pre-processor issues that Stephen mentioned aren't trivial. Let's undupe and mark it blocked on __annotation. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=30932 [Bug 30932] unresolved external symbol ___annotation -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34198] New: Potential leaks reported on `new`ed pointer escaped via reinterpret_cast + bit ops
https://bugs.llvm.org/show_bug.cgi?id=34198
Bug ID: 34198
Summary: Potential leaks reported on `new`ed pointer escaped
via reinterpret_cast + bit ops
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Static Analyzer
Assignee: kreme...@apple.com
Reporter: george.burgess...@gmail.com
CC: llvm-bugs@lists.llvm.org
Test case:
using uintptr_t = unsigned long long;
uintptr_t bar;
void alloc() {
bar = reinterpret_cast(new int) | 0;
}
$ clang --analyze /tmp/tc.cpp -fno-exceptions
/tmp/tc.cpp:4:7: warning: Potential memory leak
bar = reinterpret_cast(new int) | 0;
^~
$
However, if the test-case is changed to:
using uintptr_t = unsigned long long;
uintptr_t bar;
void alloc() {
bar = reinterpret_cast(new int);
bar |= 0;
}
This "potential leak" warning doesn't appear, regardless of the value that
`bar` is `or`ed with.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34199] New: Unit tests fail with symbol versioning and -DCMAKE_SHARED_LINKER_FLAGS="-Wl, -Bsymbolic -static-libstdc++
https://bugs.llvm.org/show_bug.cgi?id=34199 Bug ID: 34199 Summary: Unit tests fail with symbol versioning and -DCMAKE_SHARED_LINKER_FLAGS="-Wl,-Bsymbolic -static-libstdc++ Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Core LLVM classes Assignee: unassignedb...@nondot.org Reporter: tstel...@gmail.com CC: llvm-bugs@lists.llvm.org, sylves...@debian.org This is a regression caused by r300496. Building with -DCMAKE_SHARED_LINKER_FLAGS="-Wl,-Bsymbolic -static-libstdc++ causes 437 unit test failures. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 33849] [meta] 5.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=33849 Bug 33849 depends on bug 34107, which changed state. Bug 34107 Summary: (Windows) ARM division libcall handling broken - result registers clobbered? https://bugs.llvm.org/show_bug.cgi?id=34107 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34107] (Windows) ARM division libcall handling broken - result registers clobbered?
https://bugs.llvm.org/show_bug.cgi?id=34107 Quentin Colombet changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Quentin Colombet --- Pushed the fix in r310979. Thanks Martin for spotting the typo. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34200] New: lld self hosting failure: unknown option: -function-sections, -data-sections
https://bugs.llvm.org/show_bug.cgi?id=34200 Bug ID: 34200 Summary: lld self hosting failure: unknown option: -function-sections, -data-sections Product: lld Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: release blocker Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: matthias.krue...@famsik.de CC: llvm-bugs@lists.llvm.org It looks like the ubuntu lto lld/llvm/clang selfhost bot is failing since r310827 http://lab.llvm.org:8011/builders/clang-with-lto-ubuntu/builds/4272 It fails with 13.823 [3342/32/239] Linking CXX executable bin/llvm-tblgen FAILED: bin/llvm-tblgen : && /home/buildslave/buildslave1a/clang-with-lto-ubuntu/install/stage2/bin/clang++ -fPIC -fvisibility-inlines-hidden -Werror -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -fcolor-diagnostics -ffunction-sections -fdata-sections -flto -O3 -fuse-ld=lld -Wl,--color-diagnostics -flto -Wl,-allow-shlib-undefined -Wl,-rpath-link,/home/buildslave/buildslave1a/clang-with-lto-ubuntu/build/stage3/./lib -Wl,-O3 -Wl,--gc-sections utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/AsmMatcherEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/AsmWriterEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/AsmWriterInst.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/Attributes.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CallingConvEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeEmitterGen.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenDAGPatterns.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenInstruction.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenMapTable.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenRegisters.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenSchedule.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CodeGenTarget.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelMatcherEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelMatcherGen.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelMatcherOpt.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DAGISelMatcher.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DFAPacketizerEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/DisassemblerEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/FastISelEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/FixedLenDecoderEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/GlobalISelEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/InstrInfoEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/IntrinsicEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/OptParserEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/PseudoLoweringEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/RegisterBankEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/RegisterInfoEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/SearchableTableEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/SubtargetEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/SubtargetFeatureInfo.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/TableGen.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/Types.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86DisassemblerTables.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86EVEX2VEXTablesEmitter.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86ModRMFilters.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/X86RecognizableInstr.cpp.o utils/TableGen/CMakeFiles/obj.llvm-tblgen.dir/CTagsEmitter.cpp.o -o bin/llvm-tblgen -Wl,-rpath,"\$ORIGIN/../lib" lib/libLLVMSupport.a lib/libLLVMTableGen.a -lpthread lib/libLLVMSupport.a -lrt -ldl -ltinfo -lpthread -lm lib/libLLVMDemangle.a && : /home/buildslave/buildslave1a/clang-with-lto-ubuntu/install/stage2/bin/ld.lld: error: --plugin-opt: unknown option: mcpu=x86-64 /home/buildslave/buildslave1a/clang-with-lto-ubuntu/install/stage2/bin/ld.lld: error: --plugin-opt: unknown option: -function-sections /home/buildslave/buildslave1a/clang-with-lto-ubuntu/install/stage2/bin/ld.lld: error: --plugin-opt: unknown option: -data-sections clang-6.0: error: linker command failed with exit code 1 (use -v to see invocation) here: http://lab.llvm.org:8011/builders/clang-with-lto-ubuntu/builds/4272/steps/build-stage3-compiler/logs/stdio I can also reproduce this locally when trying to boostrap latest git with llvm/clang/lld -- You are receiving this mail because: You are on the CC list for the bug.
[llvm-bugs] [Bug 34202] New: Backport r310979 to 5.0
https://bugs.llvm.org/show_bug.cgi?id=34202 Bug ID: 34202 Summary: Backport r310979 to 5.0 Product: libraries Version: 5.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: mar...@martin.st CC: llvm-bugs@lists.llvm.org Please backport r310979 to 5.0, fixing PR34107 for the release branch. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34203] New: LNT Makefile test-suite build (lnt runtest nt) fails after r310975
https://bugs.llvm.org/show_bug.cgi?id=34203 Bug ID: 34203 Summary: LNT Makefile test-suite build (lnt runtest nt) fails after r310975 Product: Test Suite Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Nightly Tester Assignee: unassignedb...@nondot.org Reporter: elad2.co...@intel.com CC: llvm-bugs@lists.llvm.org Running the test-suite using the Makefile driver (i.e. "lnt runtest nt") fails after the commit r310975. (a CMake driver run, i.e. "lnt runtest test-suite" works). The buildbots that run the test-suite are currently red. Failure while running nightly tests! See log: /home/buildslave/buildslave/clang-native-arm-lnt/test/sandbox/build/test.log ... make[1]: Target 'test' not remade because of errors. make[1]: Leaving directory '/home/buildslave/buildslave/clang-native-arm-lnt/test/sandbox/build' Makefile.programs:954: recipe for target 'report.simple.raw.out' failed make: *** [report.simple.raw.out] Error 2 Combining the fact that only the Makefile based run is failing, and looking into https://reviews.llvm.org/rL310975 it seems that the patch is missing a Makefile in the inner most level (i.e. MultiSource/Benchmarks/DOE-ProxyApps-C++/PENNANT/Makefile). I think we'll have to revert the patch unless Hal or jiseung can commit an immediate fix. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
