search for: compilerrt

...erforming Test HAVE_SYNC_BOOL_COMPARE_AND_SWAP_INT - Success -- Performing Test HAVE_SYNC_BOOL_COMPARE_AND_SWAP_LONG -- Performing Test HAVE_SYNC_BOOL_COMPARE_AND_SWAP_LONG - Success -- Configuring done -- Generating done ~~~~~Build Warnings During Make~~~~~ [ 4%] Building C object lib/CMakeFiles/CompilerRT-Generic.dir/ashldi3.c.o /home/taylorh/prog/compiler-rt/lib/ashldi3.c:22: warning: ISO C does not allow extra ‘;’ outside of a function ~~~~~Note: Identical warnings in the following files~~~~~ [ 5%] Building C object lib/CMakeFiles/CompilerRT-Generic.dir/ashrdi3.c.o [ 12%] Building C object lib/CM...

...forming Test HAVE_SYNC_BOOL_COMPARE_AND_SWAP_INT - Success -- Performing Test HAVE_SYNC_BOOL_COMPARE_AND_SWAP_LONG -- Performing Test HAVE_SYNC_BOOL_COMPARE_AND_SWAP_LONG - Success CMake Warning (dev) at test/CMakeLists.txt:8 (TARGET_LINK_LIBRARIES): Cannot specify link libraries for target "CompilerRT" which is not built by this project. CMake does not support this but it used to work accidentally and is being allowed for compatibility. Policy CMP0016 is not set: target_link_libraries() reports error if only argument is not a target. Run "cmake --help-policy CMP0016"...

...g - compiler-rt build systems relationship with this. > > Regarding the use of ExternalProject within Clang, I think it could > create more problems than it solves. For one, it can't be used from > within the monolithic build (unless you have a duplicate llvm build, > or point CompilerRT to a subset of the currently-building LLVM build). > Could you elaborate on this? That's exactly what I'm trying to do now - when I call "ExternalProject_Add(compiler-rt)" from Clang build tree, I use just-built llvm-config to configure it, and set up the paths so that "m...

Hello folks! I just wanted to give everyone a heads up about this. I spoke with Doug about this about a month ago and he told me to charge boldly forward, so the commits will be flying RSN. Essentially, the compiler-rt CMake build system is largely non-functional. Major portions are just commented out, I couldn't get it to actually build anything. Daniel has mostly been maintaining and

...ncremental > strategy. For instance, how about starting by moving the call > 'add_llvm_external_project(compiler-rt)' from > llvm/projects/CMakesLists.txt to clang/runtime? We can tweak this > macro (or a clang variant) to optionally do something like: > > include(AddCompilerRt) > > That way if CMAKE_PREFIX_PATH includes a path to the compiler-rt > install directory, it can import all the same build targets that would > be created by add_subdirectory(compiler-rt). > Probably I don't understand how CMAKE_PREFIX_PATH works. How can top-level targets from...

That's great. For multi targets compilerrt-rts, in old llvm 3.5 configuremakefileconfigure/makefile system, it will build multiple libs for each target on the target list pass to clang building. but since you said compiler-rt now require sysroot for proper headers, then I don't think multi libs can be built together any more. However,...

...s talk about the options for supporting this case. A) We could require the host compiler to have support for -faddress-sanitizer, but ensure that the just-built runtime library is used rather than the host compiler's runtime library. B) We can depend upon the Clang built in the same LLVM/Clang/CompilerRT checkout, and provide a custom compilation strategy to use it to instrument the unittest code. Option A has fairly obvious problems: it introduces version skew into the equation, and would require a full bootstrap to test new instrumentation. However, it plays very nicely with the build system, r...

...case. >> >> A) We could require the host compiler to have support for >> -faddress-sanitizer, but ensure that the just-built runtime library is used >> rather than the host compiler's runtime library. >> B) We can depend upon the Clang built in the same LLVM/Clang/CompilerRT >> checkout, and provide a custom compilation strategy to use it to instrument >> the unittest code. >> >> >> Option A has fairly obvious problems: it introduces version skew into the >> equation, and would require a full bootstrap to test new instrumentation. &g...

...> >>> A) We could require the host compiler to have support for > -faddress-sanitizer, but ensure that the just-built runtime library is used > rather than the host compiler's runtime library. > >>> B) We can depend upon the Clang built in the same > LLVM/Clang/CompilerRT checkout, and provide a custom compilation strategy > to use it to instrument the unittest code. > >>> > >>> > >>> Option A has fairly obvious problems: it introduces version skew into > the equation, and would require a full bootstrap to test new > inst...

...g this case. >>> >>> A) We could require the host compiler to have support for -faddress-sanitizer, but ensure that the just-built runtime library is used rather than the host compiler's runtime library. >>> B) We can depend upon the Clang built in the same LLVM/Clang/CompilerRT checkout, and provide a custom compilation strategy to use it to instrument the unittest code. >>> >>> >>> Option A has fairly obvious problems: it introduces version skew into the equation, and would require a full bootstrap to test new instrumentation. However, it plays...

...> supporting this case. > > A) We could require the host compiler to have support for > -faddress-sanitizer, but ensure that the just-built runtime library is used > rather than the host compiler's runtime library. > B) We can depend upon the Clang built in the same LLVM/Clang/CompilerRT > checkout, and provide a custom compilation strategy to use it to instrument > the unittest code. > > > Option A has fairly obvious problems: it introduces version skew into the > equation, and would require a full bootstrap to test new instrumentation. > However, it plays ver...

...gt;> >> >>> A) We could require the host compiler to have support for -faddress-sanitizer, but ensure that the just-built runtime library is used rather than the host compiler's runtime library. >> >>> B) We can depend upon the Clang built in the same LLVM/Clang/CompilerRT checkout, and provide a custom compilation strategy to use it to instrument the unittest code. >> >>> >> >>> >> >>> Option A has fairly obvious problems: it introduces version skew into the equation, and would require a full bootstrap to test new instrum...

...;>> A) We could require the host compiler to have support for > -faddress-sanitizer, but ensure that the just-built runtime library is used > rather than the host compiler's runtime library. > >> >>> B) We can depend upon the Clang built in the same > LLVM/Clang/CompilerRT checkout, and provide a custom compilation strategy > to use it to instrument the unittest code. > >> >>> > >> >>> > >> >>> Option A has fairly obvious problems: it introduces version skew > into the equation, and would require a full boot...

On 1/22/2013 1:49 AM, Anton Korobeynikov wrote: >> What can I do? > Just don't build compiler-rt. And yes, instructions should be modified > to outline that compiler-rt is optional step. > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematics and Mechanics, Saint Petersburg State University > _______________________________________________ > LLVM

> On May 5, 2016, at 12:11 PM, Renato Golin <renato.golin at linaro.org> wrote: > > On 5 May 2016 at 19:33, Chris Bieneman via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> I have a patch out for review now (http://reviews.llvm.org/D19742) that >> allows building builtins without a full toolchain. > > Nice! Does that also allow you to build multiple

Hi Jordan, I've committed my changes to hook up the BlocksRuntime/ subdirectory of compiler-rt, using CMake. The cmake build process is documented at <http://llvm.org/docs/CMake.html > More specifically, to use this support on FreeBSD, for example, you would do: 1) Install cmake (<http://www.cmake.org/>), add it to your PATH 2) Check out the source code for llvm and clang

Clang does indeed built it with one warning. [ 55%] Building C object lib/CMakeFiles/CompilerRT-Common.dir/gcc_personality_v0.c.o /export/home/edward/lab/llvm/build/compiler-rt/lib/gcc_personality_v0.c:232:36: warning: implicit declaration of function '__builtin_eh_return_data_regno' is invalid in C99 [-Wimplicit-function-declaration] _Unwind_SetGR(context, __builtin...

...could require the host compiler to have support for >> -faddress-sanitizer, but ensure that the just-built runtime library is used >> rather than the host compiler's runtime library. >> >> >>> B) We can depend upon the Clang built in the same >> LLVM/Clang/CompilerRT checkout, and provide a custom compilation strategy >> to use it to instrument the unittest code. >> >> >>> >> >> >>> >> >> >>> Option A has fairly obvious problems: it introduces version skew >> into the equation, and would...

The Blocks language and implementation specifications are checked into clang/docs. More generally, on Mac OS X, the blocks runtime is linked into the C library ("libSystem"), and available to the entire OS. Clients that create blocks may implicitly get compiler-generated calls to some of the runtime functions, and the developer may also make explicit calls to, e.g.,

...nt if none of the supported mechanisms are found. I'll look at that. Thanks for the feedback! Shantonu Sent from my MacBook On Sep 22, 2009, at 9:01 PM, Edward O'Callaghan wrote: > Clang does indeed built it with one warning. > > [ 55%] Building C object > lib/CMakeFiles/CompilerRT-Common.dir/gcc_personality_v0.c.o > /export/home/edward/lab/llvm/build/compiler-rt/lib/ > gcc_personality_v0.c:232:36: > warning: implicit declaration of function > '__builtin_eh_return_data_regno' is invalid in C99 > [-Wimplicit-function-declaration] > _U...