search for: llvm_build_external_compiler_rt

Folks, I'm at a loss trying to add Compiler-RT to an LLVM build, even after checking out the instructions at http://compiler-rt.llvm.org, so I'd appreciate your help. I've tried adding the CMake options LLVM_ENABLE_PROJECTS, LLVM_BUILD_EXTERNAL_COMPILER_RT, LLVM_EXTERNAL_COMPILER_RT_SOURCE_DIR, CLANG_DEFAULT_RTLIB. All to no avail. FWIW, I'm building for the targets AArch64, ARM and X86. Feeling like a newbie makes me want to cry... :-} Thank you, -- Evandro Menezes

...Folks, >> >> I'm at a loss trying to add Compiler-RT to an LLVM build, even after >> checking out the instructions at http://compiler-rt.llvm.org, so I'd >> appreciate your help. >> >> I've tried adding the CMake options LLVM_ENABLE_PROJECTS, >> LLVM_BUILD_EXTERNAL_COMPILER_RT, LLVM_EXTERNAL_COMPILER_RT_SOURCE_DIR, >> CLANG_DEFAULT_RTLIB. All to no avail. > > You'll need to give a lot more details on what you tried, and how it > failed. Without that information, nobody can really help you. OK, what else can I say? I checked out the projects side by...

On 28 May 2014 17:44, Justin Bogner <mail at justinbogner.com> wrote: > In the autoconf system, I'm pretty sure compiler-rt's build is triggered > by a Makefile in clang, tools/clang/runtime/compiler-rt/Makefile. This > Makefile comments "We currently only try to generate runtime libraries > on x86", so I guess that's the place to start if you want to get it

...Android platform - IIRC build rules for Android are much simpler than for Darwin/Linux, and assume that build tree will be properly configured to build a single compiler-rt runtime for a specific triple. Probably this is the approach you want to eventually use for another platforms. Also check out LLVM_BUILD_EXTERNAL_COMPILER_RT flag, which is an attempt to use ExternalProject to recursively call CMake from LLVM/Clang build tree. It doesn't iterate over all the target triples we want/can support, though. It had some problems with Ninja, though. I'd also prefer to not move host==target to a special case, at least a...

...014 12:43 PM, Alexey Samsonov wrote: > > Do you think it makes sense to land my ExternalProject_Add patch > > so that others can experiment with it? I can add quit with a > > fatal_error/warning if the build tree rules are generated with Ninja. > > Since it is conditional on LLVM_BUILD_EXTERNAL_COMPILER_RT, yes. > Submitted as r202367. > > > parallelism doesn't work when I run "make check-compiler-rt -j8" > > in the original build tree, presumably because we call > > "cd /path/to/compiler-rt/build/tree && make check-all" there. > > Righ...

...quite the experiment. Looking at > clang/runtime/CMakeLists.txt, I'm not seeing a lot of bang for buck > here, and it looks like this file is prone to bit rot. Could you please elaborate on this? In fact, I don't plan to give up on this experiment. On the contrary, I wanted to move LLVM_BUILD_EXTERNAL_COMPILER_RT to the bots, migrate the workflow of our team to use this mode, and eventually make it the default. The problem is that we want top-level targets from compiler-rt build tree be visible in the llvm/clang top-level build tree. I thought this could be achieved by ugly propagation of top-level compile...

...I need the realtime project to be built. I did download the llvm/projects/compiler-rt source, but the Makefile in llvm/projects filters it out: # Don't build compiler-rt, it isn't designed to be built directly. DIRS := $(filter-out compiler-rt,$(DIRS)) The main source dir of llvm has an LLVM_BUILD_EXTERNAL_COMPILER_RT option, but I wasn't sure if I that would put RT support into clang (which I'd like) or rather, irf it would build a separate RT compiler. Can you guys advise me how to build clang on Linux so that _Block_copy will be useable? Thank you, David -------------- next part -------------- A n...

Hi Brad, Thanks for investigating this. Do you think it makes sense to land my ExternalProject_Add patch so that others can experiment with it? I can add quit with a fatal_error/warning if the build tree rules are generated with Ninja. However, there is a problem with Unix Makefiles as well: parallelism doesn't work when I run "make check-compiler-rt -j8" in the original build tree,

...it does. There was no equivalent of that flag in autoconf. The autoconf —enable-shared option maps to LLVM_BUILD_LLVM_DYLIB=On in CMake. For 25665, we will need to add an option to skip generating targets for libcxx’s library. I can work that up today or tomorrow. Also, make sure you are setting LLVM_BUILD_EXTERNAL_COMPILER_RT=On. If you don’t set that you’re not building libclang_rt with the just-built compiler. If you have other questions please let me know. I can also share our internal packaging scripts with you off-list if you'd like. I don’t think there is anything really secret in them, they’re just not usefu...

...${CMAKE_CURRENT_SOURCE_DIR}/libcxxabi) AND (NOT ${entry} STREQUAL ${CMAKE_CURRENT_SOURCE_DIR}/libunwind)) @@ -26,6 +27,9 @@ add_llvm_external_project(libcxx) add_llvm_external_project(libunwind) endif() + if(NOT MSVC) + add_llvm_external_project(openmp) + endif() if(NOT LLVM_BUILD_EXTERNAL_COMPILER_RT) add_llvm_external_project(compiler-rt) endif() checked into llvm trunk to complete the integration of the openmp build into the llvm cmake build? The proposed patch from that message works fine with current openmp and llvm svn. Jack -------------- next part -------------- An HTM...

...argets being created for projects (we don’t really use this, and anywhere we are is probably a bug) (3) Some projects have special handling. For example test-suite isn’t actually treated as a project, it has special handling in LLVM/CMakeLists.txt:727, and Compiler-RT is handled by clang if you set LLVM_BUILD_EXTERNAL_COMPILER_RT=On. With this in mind I was thinking about the general usability of our build system. The distinction between a project and a tool is not very clear. At a high level I see three different use cases that are covered by our current projects & tools directories. (1) Projects that are configured...

...s.txt, I'm not seeing a lot of bang for buck > >> here, and it looks like this file is prone to bit rot. > > > > > > Could you please elaborate on this? In fact, I don't plan to give up on > this > > experiment. > > On the contrary, I wanted to move LLVM_BUILD_EXTERNAL_COMPILER_RT to the > > bots, migrate the workflow of our team to use this mode, and eventually > make > > it the default. > > > > The problem is that we want top-level targets from compiler-rt build > tree be > > visible in the llvm/clang > > top-level build tree. I th...

...did download the llvm/projects/compiler-rt source, but the Makefile in llvm/projects filters it out: >> >> # Don't build compiler-rt, it isn't designed to be built directly. >> DIRS := $(filter-out compiler-rt,$(DIRS)) >> >> The main source dir of llvm has an LLVM_BUILD_EXTERNAL_COMPILER_RT option, but I wasn't sure if I that would put RT support into clang (which I'd like) or rather, irf it would build a separate RT compiler. >> >> Can you guys advise me how to build clang on Linux so that _Block_copy will be useable? >> >> Thank you, >> >&...

...ing created for projects (we don’t really use this, and anywhere we are is probably a bug) >> (3) Some projects have special handling. For example test-suite isn’t actually treated as a project, it has special handling in LLVM/CMakeLists.txt:727, and Compiler-RT is handled by clang if you set LLVM_BUILD_EXTERNAL_COMPILER_RT=On. >> >> With this in mind I was thinking about the general usability of our build system. The distinction between a project and a tool is not very clear. At a high level I see three different use cases that are covered by our current projects & tools directories. >>...

On 29 November 2015 at 01:50, Jeremy Huddleston Sequoia <jeremyhu at apple.com> wrote: > >> On Nov 16, 2015, at 05:30, Alex Bradbury via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> * LLVM's autoconf-based build system is now officially deprecated, with the >> CMake build system being preferred. >> [r252520](http://reviews.llvm.org/rL252520).

Submitted r204593. On Sun, Mar 23, 2014 at 10:03 PM, Alexey Samsonov <samsonov at google.com>wrote: > Hi Dmitri, > > On Sat, Mar 22, 2014 at 11:50 PM, Dmitri Gribenko <gribozavr at gmail.com>wrote: > >> Hello, >> >> It looks like compiler-rt CMake scripts don't take CMAKE_CXX_FLAGS >> into account. This is because clang_compile and

...ted for projects (we don’t really use this, and anywhere we are is probably a bug) >>>> (3) Some projects have special handling. For example test-suite isn’t actually treated as a project, it has special handling in LLVM/CMakeLists.txt:727, and Compiler-RT is handled by clang if you set LLVM_BUILD_EXTERNAL_COMPILER_RT=On. >>>> >>>> With this in mind I was thinking about the general usability of our build system. The distinction between a project and a tool is not very clear. At a high level I see three different use cases that are covered by our current projects & tools directories....

This is definitely a concern. That’s why I had proposed not treating “host” as a cross-target. Handling building compiler-rt for host differently makes one of the common cases better. WRT Ninja. Ninja’s pooling capabilities actually should solve some of the problems you’re voicing. In particular, we can make the cross-builds fall into the “console” pool to prevent ninja from over-saturating the

On Wed, Mar 8, 2017 at 2:03 PM Sterling Augustine <saugustine at google.com> wrote: > Yes, this is a aspect of the larger problem that clang bootstrap doesn't > work for a cross-compiler. The build (mostly?) assumes that host==target > during the build of clang itself, and then if you want another architecture > also, you run a second build of the target libraries, and

So, we’ve had this conversation a few times, and I wanted to coalate a status report for all the interested parties. Here's the outstanding work and my (not necissarily correct) view of the status and importance of each one: * Bug 12157 - llvmconfig.cmake.in make cmake installations not relocatable - There are patches on the bug that we should review, test, and land * Bug 14109 - CMake