search for: llvm_default_target_triple

...gr.jp/console Each of them (test-*-linux) is doing; - Assume a preceding builder passes with warming ccache. - All compilation units will hit ccache whenever the tree is built before lit. - Almost all compilation units will hit ccache except for Host.cpp when the tree is built with different LLVM_DEFAULT_TARGET_TRIPLE. FYI, I am doing a trick to let ccache recognize compilation units identical for build.ninja; $ sed -i -r 's=(-I|_COMPILER\S* )/home/bb/\w[^/]*/llvm-project=\1../llvm-project=g' build.ninja In other words, testing builders have almost same build except for Host.cpp. I have to build the...

I've been working on getting the LLVM OpenMP library to build smoothly alongside llvm/clang using CMake, but one problem I'm having is determining exactly which CMake option designates the architecture the compiler will compile. I see LLVM_TARGET_ARCH, LLVM_TARGETS_TO_BUILD, LLVM_DEFAULT_TARGET_TRIPLE, etc. I thought I should just ask which one designates the architecture the compiler will build, but I wouldn't mind an explanation for all of them :) And yes, I've looked at http://llvm.org/docs/CMake.html, but am still confused. Any help is greatly appreciated! -- Johnny -------------...

720beaedce6f19c81156fe20168f85989a8db53d CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CMakeLists.txt b/CMakeLists.txt index bb70f15..e327427 100644 --- a/CMakeLists.txt +++ b/CMakeLists.txt @@ -249,7 +249,7 @@ set(LLVM_DEFAULT_TARGET_TRIPLE "${LLVM_HOST_TRIPLE}" CACHE STRING set(TARGET_TRIPLE "${LLVM_DEFAULT_TARGET_TRIPLE}") include(HandleLLVMOptions) - +set(Python_ADDITIONAL_VERSIONS 2.7 2.6 2.5 2.4) # Verify that we can find a Python interpreter, include(FindPythonInterp) if( NOT PYTHONINTERP_FOUND ) --...

...end. > > I would love to do this, but there’s a bug in the backend which causes a few of the Generic CodeGen tests to fail. To work around this, I leave X86 as the default target for now. I’m definitely planning on updating this once I’ve fixed the bug. > > This usually happens when LLVM_DEFAULT_TARGET_TRIPLE is not explicitely set and you end up with your host machine as default while not building the x86 target. If you set LLVM_DEFAULT_TARGET_TRIPLE to some AVR ones the failure should go away (otherwise complain and file bugs). - Matthias -------------- next part -------------- An HTML attachment wa...

Hello, I was looking at sys::getDefaultTargetTriple() (file: lib/Support/Unix/Host.inc ) and there is something unclear to me. std::string sys::getDefaultTargetTriple() { StringRef TargetTripleString(LLVM_DEFAULT_TARGET_TRIPLE); std::pair<StringRef, StringRef> ArchSplit = TargetTripleString.split('-'); // Normalize the arch, since the target triple may not actually match the // target. std::string Arch = ArchSplit.first; std::string Triple(Arch); Triple += '-'; Triple += ArchSp...

...Studio 12" generator. My cmake configuration goes like >> Set path, include and lib environment variables to point to zlib headers and libraries. Cmake version is 2.8.12.2 cmake -G "Visual Studio 12" -D LLVM_TARGETS_TO_BUILD:STRING=%TARG% -D TARGET_TRIPLE:STRING=%TRIPLE% -D LLVM_DEFAULT_TARGET_TRIPLE:STRING=%TRIPLE% -D LLVM_TARGET_ARCH:STRING=%TRIPLE% -D LLVM_ENABLE_PIC:BOOL=ON -D LLVM_ENABLE_ASSERTIONS:BOOL=ON -D CMAKE_INSTALL_PREFIX=%win_top_install_dir% -D CMAKE_BUILD_TYPE=%BLDMODE% -DLLVM_APPEND_VC_REV:BOOL=ON -D LLVM_VENDOR_NAME:STRING=%NAME% -D LLVM_VENDOR_VERSION:STRING=%VER% %win_top_sr...

...iler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. I'm trying to configure with the following options: CLANG_DEFAULT_CXX_STDLIB = libc++ CLANG_DEFAULT_RTLIB = compiler-rt LIBCXX_CXX_ABI = libcxxabi LLVM_DEFAULT_TARGET_TRIPLE = x86_64-pc-linux-musl LIBCXXABI_TARGET_TRIPLE = x86_64-pc-linux-musl LIBUNWIND_TARGET_TRIPLE = x86_64-pc-linux-musl DEFAULT_SYSROOT = /path/to/musl GCC_INSTALL_PREFIX = /path/to/gcc-stub LLVM_TARGETS_TO_BUILD = X86 LIBCXXABI_USE_COMPILER_RT = ON LIBCXXABI_USE_LLVM_UNWIN...

...l-based toolchain. >> >> The configuration is the following: >> >> LIBCXX_HAS_MUSL_LIBC=ON >> LIBCXX_HAS_GCC_S_LIB=OFF >> CLANG_DEFAULT_CXX_STDLIB=libc++ >> CLANG_DEFAULT_LINKER=lld >> CLANG_DEFAULT_RTLIB=compiler-rt >> LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl >> LLVM_TARGET_ARCH=x86_64 >> LLVM_TARGETS_TO_BUILD=X86 >> >> When linking libc++.so there are a lot of undefined references to __cxa_allocate_exception, __cxa_begin_catch, __cxa_end_catch, __cxa_free_exception, __cxa_guard_abort, __cxa_guard_ac...

...iler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. I'm trying to configure with the following options: CLANG_DEFAULT_CXX_STDLIB = libc++ CLANG_DEFAULT_RTLIB = compiler-rt CLANG_DEFAULT_LINKER = lld LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl I use cmake to configure and ninja to build. It configures fine and builds, but I need libcompiler_rt.so and it is not among build targets, so it is not built and installed. I think it is a bug and libcompiler_rt.so should be built. I don't have a bugzilla account, so I...

...versions cloned from GitHub mirror, branch `master`. >>> >>> I'm trying to configure with the following options: >>> CLANG_DEFAULT_CXX_STDLIB = libc++ >>> CLANG_DEFAULT_RTLIB = compiler-rt >>> CLANG_DEFAULT_LINKER = lld >>> LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl >>> >>> I use cmake to configure and ninja to build. >>> >>> It configures fine and builds, but I need libcompiler_rt.so and it is not among build targets, so it is not built and installed. >>> >>> I think it is a bug...

...abi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. > > I'm trying to configure with the following options: > CLANG_DEFAULT_CXX_STDLIB = libc++ > CLANG_DEFAULT_RTLIB = compiler-rt > CLANG_DEFAULT_LINKER = lld > LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl > > I use cmake to configure and ninja to build. > > It configures fine and builds, but I need libcompiler_rt.so and it is not among build targets, so it is not built and installed. > > I think it is a bug and libcompiler_rt.so should be built. I don't...

...ild LLVM, Clang, LLD, compiler-rt, libc++, libc++abi and libunwind with musl-based toolchain. The configuration is the following: LIBCXX_HAS_MUSL_LIBC=ON LIBCXX_HAS_GCC_S_LIB=OFF CLANG_DEFAULT_CXX_STDLIB=libc++ CLANG_DEFAULT_LINKER=lld CLANG_DEFAULT_RTLIB=compiler-rt LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl LLVM_TARGET_ARCH=x86_64 LLVM_TARGETS_TO_BUILD=X86 When linking libc++.so there are a lot of undefined references to __cxa_allocate_exception, __cxa_begin_catch, __cxa_end_catch, __cxa_free_exception, __cxa_guard_abort, __cxa_guard_acquire, __cxa_guard_release, __cxa_...

...ory). All are the latest versions cloned from GitHub mirror, branch `master`. >> >>  I'm trying to configure with the following options: >>     CLANG_DEFAULT_CXX_STDLIB = libc++ >>     CLANG_DEFAULT_RTLIB = compiler-rt >>     CLANG_DEFAULT_LINKER = lld >>     LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl >> >>  I use cmake to configure and ninja to build. >> >>  It configures fine and builds, but I need libcompiler_rt.so and it is not among build targets, so it is not built and installed. >> >>  I think it is a bug and libcompiler_rt.so shoul...

Can you also please tell me how can I find out the ABI (application binary interface)? Thanks,Iulia On Monday, June 5, 2017 8:58 PM, Bruce Hoult <bruce at hoult.org> wrote: grep name /proc/cpuinfo Then look up the model number in https://en.wikipedia.org/wiki/List_of_Intel_Xeon_microprocessors On Mon, Jun 5, 2017 at 8:41 PM, Iulia Stirb via llvm-dev <llvm-dev at

...; CXX='clang++' cmake -G Ninja ../llvm-source-code >> -DCMAKE_CROSSCOMPILING=True >> -DCMAKE_INSTALL_PREFIX=./llvm >> -DLLVM_TABLEGEN=/home/lab/workspace/llvm/build4x86/bin/llvm-tblgen >> -DCLANG_TABLEGEN=/home/lab/workspace/llvm/build4x86/bin/clang-tblgen >> -DLLVM_DEFAULT_TARGET_TRIPLE=arm-linux-gnueabihf >> -DLLVM_TARGET_ARCH=ARM >> -DLLVM_TARGETS_TO_BUILD=ARM >> -DCMAKE_CXX_FLAGS='-target armv7a-linux-gnueabihf -mcpu=cortex-a9 >> -I/usr/arm-linux-gnueabihf/include/c++/4.7.3/arm-linux-gnueabihf/ >> -I/usr/arm-linux-gnueabihf/include/ >> -I...

Hi, What is the Cmake equivalent to configures target option [ ./configure --target=avr-atmel-none] ? --John -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120710/5405f54b/attachment.html>

...rrors MSVC was giving). Anyway, your ABI will be determined by which OS you're compiling for in almost all cases. And if you're building Clang on the same platform you're running the binaries on that should be correctly detected when you run CMake. Otherwise you'll have to set the LLVM_DEFAULT_TARGET_TRIPLE CMake variable. Typical values are "x86_64-linux-gnu", "x86_64-apple-macosx10.12" or "x86_64-windows-msvc". That will also set the corresponding ABI. Cheers. Tim. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.l...

> On Feb 3, 2017, at 4:18 AM, Tobias Grosser via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Fri, Feb 3, 2017, at 11:37 AM, Dylan McKay via llvm-dev wrote: >> Hey all, >> >> Every few weeks, a change is committed to trunk that breaks the AVR >> buildbot. >> >> A problem presents when commit authors do not fix the build, and just

I'm trying to build LLVM on Windows 10 for x86_64. The cmake cmdline I used is c:\cmake-3.8.0-rc1-win64-x64\bin\cmake.exe -DLLVM_TARGETS_TO_BUILD=x86_64 -G "Visual Studio 14" . And this ultimately gives me: llvm-build: error: invalid target to enable: 'x86_64' (not in project) The source I'm trying to build is the llvm-3.8.0.src.tar.xz I got from

Thanks! It looks like this is sorted out now. On Thu, Jan 4, 2018 at 5:07 PM, Friedman, Eli <efriedma at codeaurora.org> wrote: > On 1/4/2018 4:51 PM, Adrian McCarthy via llvm-dev wrote: > > I tried to land a small fix before going on vacation at the end of the > year, but I had to revert it because it broke on a few of the build bots, > specifically