search for: dhinton

I believe what's happening here is that clang translates the -fuse-ld=lld into calling the ld.lld executable, which is actually the ELF LLD linker, not the Mach-O one. On 6.0, the Mach-O linker symlink is called ld64.lld instead (and clang has been changed to call out to that name) to disambiguate the two. For 5.0, I'm not sure how best to force the Mach-O linker (I'm not familiar with

Hi. I'm using LLVM 5.0.1 on macOS 10.12. I have a very simple program (program.c): int main() {} When attempting to compile with LLD, I get this output: $ clang -fuse-ld=lld program.c /opt/llvm/5.0.1/bin/ld.lld: error: unknown argument: -no_deduplicate /opt/llvm/5.0.1/bin/ld.lld: error: unknown argument: -dynamic /opt/llvm/5.0.1/bin/ld.lld: error: unknown argument: -arch

Hi Timo: You need to find LLVMConfig.cmake in the binary or install directory tree, not the source tree. Although I don't embed clang/llvm, my config might help you figure it -- clang/llvm installed under (could have used build directory) ~/usr : $ cd /Users/dhinton/projects/cover/build/ && rm -rf * && CC=~/usr/bin/clang CXX=~/usr/bin/clang++ LLVM_DIR=~/usr/lib/cmake/llvm cmake ../CVRFI/ -GNinja $ cat ../CVRFI/CMakeLists.txt cmake_minimum_required(VERSION 2.8) set(CMAKE_EXPORT_COMPILE_COMMANDS ON) set(CMAKE_RUNTIME_OUTPUT_DIRECTORY ${CMAKE_B...

...Timo: > > You need to find LLVMConfig.cmake in the binary or install directory tree, > not the source tree. > > Although I don't embed clang/llvm, my config might help you figure it -- > clang/llvm installed under (could have used build directory) ~/usr : > > $ cd /Users/dhinton/projects/cover/build/ && rm -rf * && > CC=~/usr/bin/clang CXX=~/usr/bin/clang++ LLVM_DIR=~/usr/lib/cmake/llvm > cmake ../CVRFI/ -GNinja > > $ cat ../CVRFI/CMakeLists.txt > cmake_minimum_required(VERSION 2.8) > > set(CMAKE_EXPORT_COMPILE_COMMANDS ON) > > se...

...dded twice, once for check-clang and again for check-debuginfo. Below are the minimized patches I used to reproduce and fix the problem -- based on your originals. I've verified these patches work when including debuginfo-tests in either clang/test or llvm/projects. hth... don local:/Users/dhinton/projects/llvm_project/llvm/tools/clang $ git diff master diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt index c1ac9e4f0f..8c2db7600d 100644 --- a/test/CMakeLists.txt +++ b/test/CMakeLists.txt @@ -131,3 +131,7 @@ add_lit_testsuites(CLANG ${CMAKE_CURRENT_SOURCE_DIR} add_custom_target(clang-t...

...re the minimized patches I used to reproduce and fix the problem -- based on your originals. >> >> I've verified these patches work when including debuginfo-tests in either clang/test or llvm/projects. >> >> hth... >> don >> >> >> local:/Users/dhinton/projects/llvm_project/llvm/tools/clang $ git diff master >> diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt >> index c1ac9e4f0f..8c2db7600d 100644 >> --- a/test/CMakeLists.txt >> +++ b/test/CMakeLists.txt >> @@ -131,3 +131,7 @@ add_lit_testsuites(CLANG ${CMAKE_C...

...ck-debuginfo. > > Below are the minimized patches I used to reproduce and fix the problem -- based on your originals. > > I've verified these patches work when including debuginfo-tests in either clang/test or llvm/projects. > > hth... > don > > > local:/Users/dhinton/projects/llvm_project/llvm/tools/clang $ git diff master > diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt > index c1ac9e4f0f..8c2db7600d 100644 > --- a/test/CMakeLists.txt > +++ b/test/CMakeLists.txt > @@ -131,3 +131,7 @@ add_lit_testsuites(CLANG ${CMAKE_CURRENT_SOURCE_DIR} &...

Hi all. I want to use llvm in my project and I want to make llvm a git submodule in my project. http://llvm.org/docs/CMake.html#embedding-llvm-in-your-project At this in the documentation it claims to describe how to embed llvm into a project. I tried it that way but it doesn't work, because there isn't any findLLVM.cmake in the llvm/cmake/modules directory anymore (i don't

I sorta enjoy debugging stuff like this, so if you don't mind, I'll dig into it once I get a chance -- traveling so, my access is a bit sketchy right now. I'll see if I can grab the logs and let you know if I find anything interesting. On Tue, Nov 21, 2017 at 7:04 PM, Zachary Turner <zturner at google.com> wrote: > That change was added specifically to workaround a failure