search for: llvm_targets_to_build

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 http://releases.llvm.org/download.html If I don't specify LLVM_TAR...

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 appreciat...

...fPIC ../../lib/libLLVMX86CodeGen.a: could not read symbols: Bad value collect2: error: ld returned 1 exit status I am not sure how to proceed from here.. Thanks, Frank SRC=$HOME/svn/llvm-3.8 CMAKE_BUILD_TYPE="Debug" CMAKE_INSTALL_PREFIX="$HOME/toolchain/install/llvm-3.8" LLVM_TARGETS_TO_BUILD="X86" CXX="/dist/gcc-4.8.2/bin/g++" CC="/dist/gcc-4.8.2/bin/gcc" #-DBUILD_SHARED_LIBS="ON" \ cmake -G "Unix Makefiles" \ -DCMAKE_CXX_FLAGS="-fno-rtti" \ -DCMAKE_C_FLAGS="-fno-rtti" \ -DCMAKE_CXX_COMPILER=$CXX \ -DCMAKE_C_COMP...

...impossible to figure out how to configure it with cmake without looking up online. Compare this to /src/llvm/configure --help, where I can see what the default build will look like and also how I can tweak it for what I want. Even the online documentation is kind of crappy in this regard: e.g., LLVM_TARGETS_TO_BUILD doesn't tell you *which* targets you can build in the first place. I'm sure most people who do a lot of cmake know these settings by the back of their hand, but if you're like me and totally clueless when it comes to cmake, it's downright confusing. -- Joshua Cranmer News subm...

I just checkout release_38 branches of llvm, clang and polly and built it on and x86 Ubuntu with cmake: CMAKE_BUILD_TYPE="Debug" CMAKE_INSTALL_PREFIX="$HOME/toolchain/install/llvm-3.8" LLVM_TARGETS_TO_BUILD="X86" cmake -G "Unix Makefiles" \ -DBUILD_SHARED_LIBS="ON" \ -DCMAKE_BUILD_TYPE=$CMAKE_BUILD_TYPE \ -DCMAKE_INSTALL_PREFIX=$CMAKE_INSTALL_PREFIX \ -DLLVM_TARGETS_TO_BUILD=$LLVM_TARGETS_TO_BUILD \ $SRC The build went fine, even 'make check-polly' looks okay:...

...t passed the behavior is unchanged. This patch can land today (subject to review). The second patch is a WIP, and adds support to the CMake build system for using the new tablegen flag, and for generating a new llvm/Config/llvm-targets.h header which contains defines for each target specified with LLVM_TARGETS_TO_BUILD. This new header will allow us to #ifdef code using target-specific intrinsics outside the targets, thus allowing us to strip out all the unused intrinsics. -Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: cmake-build.diff Type: application/octet-stream...

...> In terms of build system integration, I think it makes sense to do the following: > > Add a ENABLE_EXPERIMENTAL or ENABLE_STAGING flag that allows experimental features to be built (default: OFF) > Add an LLVM_STAGING_TARGETS list that contains all of the staging back-ends > Allow LLVM_TARGETS_TO_BUILD to contain a back-end from LLVM_STAGING_TARGETS *only* if ENABLE_STAGING is ON > > This will allow the default configuration to not only skip the staging back-ends, but prohibit them from being built without explicitly setting ENABLE_STAGING. Further, this will allow picking-and-choosing whi...

...tely separate compilers to produce x64 and x32 > libraries/binaries. A bit of grubbing around the internet suggests > CMake exposes this with the CMAKE_GENERATOR_PLATFORM variable, and -A > on the command line. So I'd suggest: > > c:\cmake-3.8.0-rc1-win64-x64\bin\cmake.exe > -DLLVM_TARGETS_TO_BUILD=x86_64 -G "Visual Studio 14" -A Win64 > > (plus a path to the source). That last argument is a bit of a guess, > but fits in with documentation at > https://cmake.org/cmake/help/v3.8/generator/Visual% > 20Studio%2014%202015.html > (for example). > > Hope this works...

...d wrote: > On Fri, Jul 27, 2012 at 10:54:21PM -0400, Justin Holewinski wrote: >> Add a ENABLE_EXPERIMENTAL or ENABLE_STAGING flag that allows experimental features to be built (default: OFF) >> Add an LLVM_STAGING_TARGETS list that contains all of the staging back-ends >> Allow LLVM_TARGETS_TO_BUILD to contain a back-end from LLVM_STAGING_TARGETS *only* if ENABLE_STAGING is ON > > I've submitted a patch[1] that adds this option. > > [1] http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20120730/147282.html Could we perhaps call these LLVM_ENABLE_EXPERIMENTAL and L...

On 10/7/2014 4:10 PM, Nick Kledzik wrote: > Shankar, > > Can you give provide a scenario where you want this? I’m not sure what you want here. a) LLVM could be built just for one target(LLVM_TARGETS_TO_BUILD) b) With LTO this case might happen more often, where an user would have compiled LLVM just for one architecture and lld would support other architectures that LLVM would not support. c) Printing all the targets/flavors that the linker currently supports. On Oct 7, 2014, at 2:03 PM, Shankar Easw...

...cmake configuration detect the zlib header in windows with "Visual 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 L...

> On Aug 26, 2016, at 3:22 PM, Renato Golin <renato.golin at linaro.org> wrote: > > On 26 August 2016 at 22:45, Chris Bieneman via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Recently, I’ve made a handful of new changes that actually make it useful, and I wanted to blast out this update and encourage people to give it a try. > > Woot! Compiling RT as we

...G_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_UNWINDER = ON LIBCXX_HAS_MUSL_LIBC = ON LIBCXX_USE_COMPILER_RT = ON LLVM_ENABLE_LIBCXX = ON LLVM_ENABLE_LLD = ON When I try to configure, I get the following error messages: CMake Warning at cmake/modules/HandleLLVMS...

...IBCXX_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_pure_virtual, __cxa_rethrow, __cxa_throw, __gxx_personality...

Tom Care <tcare at apple.com> writes: > This was after starting with an empty build directory. It seems to > work if I omit -DLLVM_TARGETS_TO_BUILD=X86, but a few days ago this > was working with just this target. Yep. I can replicate the problem on Linux with mkdir foo && cd foo cmake -DLLVM_TARGETS_TO_BUILD=X86 ../llvm I'll investigate a bit.

Hi, attached is a patch to improve including targets other than X86 in CMake MSVC builds. When adding libs to link, rather than always using LLVMX86CodeGen and LLVMX86AsmPrinter, it grabs the correct ones. It also adds "force-link-ints" to the various TargetMachine cpp files, as well as X86AsmPrinter and PPCAsmPrinter. These are needed to be able to encourage the Win32 linker to

...gure out how to configure it with cmake without > looking up online. Compare this to /src/llvm/configure --help, where I can > see what the default build will look like and also how I can tweak it for > what I want. Even the online documentation is kind of crappy in this regard: > e.g., LLVM_TARGETS_TO_BUILD doesn't tell you *which* targets you can build > in the first place. I'm sure most people who do a lot of cmake know these > settings by the back of their hand, but if you're like me and totally > clueless when it comes to cmake, it's downright confusing. ccmake will help...

...9;s impossible to figure out how to configure it with cmake without looking up online. Compare this to /src/llvm/configure --help, where I can see what the default build will look like and also how I can tweak it for what I want. Even the online documentation is kind of crappy in this regard: e.g., LLVM_TARGETS_TO_BUILD doesn't tell you *which* targets you can build in the first place. I'm sure most people who do a lot of cmake know these settings by the back of their hand, but if you're like me and totally clueless when it comes to cmake, it's downright confusing. Well, you can use ccmake to navi...

I certainly agree that there are a boatload of CMake options. I haven't even scratched the surface. In keeping with your suggestion: Is there a way to tell Ninja to build just one target machine? At 10/7/2020 02:58 PM, Nicolai Hähnle wrote: >Hi Paul, > >On Wed, Oct 7, 2020 at 3:33 PM Paul C. Anagnostopoulos via llvm-dev ><llvm-dev at lists.llvm.org> wrote: >>

...more exposure is best. In terms of build system integration, I think it makes sense to do the following: Add a ENABLE_EXPERIMENTAL or ENABLE_STAGING flag that allows experimental features to be built (default: OFF) Add an LLVM_STAGING_TARGETS list that contains all of the staging back-ends Allow LLVM_TARGETS_TO_BUILD to contain a back-end from LLVM_STAGING_TARGETS *only* if ENABLE_STAGING is ON This will allow the default configuration to not only skip the staging back-ends, but prohibit them from being built without explicitly setting ENABLE_STAGING. Further, this will allow picking-and-choosing which stagin...