search for: llvm_host_tripl

I'm trying to figure out how to get, from CMake, the architecture of the platform that I'm compiling LLVM for. If I'm building LLVM on x86, I want x86. On x64 I want x86_64. On arm arm. etc. The best I can figure out so far is that I should use LLVM_HOST_TRIPLE, and extract the first component of this. At least if my understanding is correct, I should have the following behavior: Compiling using 32-bit toolchain on Windows: LLVM_HOST_TRIPLE = i686-pc-win32 Compiling using 64-bit toolchain on Windows: LLVM_HOST_TRIPLE = x86_64-pc-win32 This doesn't...

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 ) -- 此致 礼 罗勇刚 Yours...

Hello, I downloaded the LLVM 10 release for windows and noticed, that the LLVM-C.dll for x86 has a size of 9kb, which seems strangely small. Both, the dll for x86 and x64, have no export directory. It is not possible to link them statically to Delphi code or call GetProcAddress on them. I do remember that this worked initially when https://reviews.llvm.org/D56774 was done when compiling the dll

This is my first post so not sure I've done everything right. Just started playing with LLVM on Windows 7, VS C++. Was trying to play with the example 4 and got the following error: "LLVM ERROR: Incompatible object format" I was able resolve the problem by following the suggestion found here:http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-December/068395.html This issue seems to

...n_ext = "@LLVM_PLUGIN_EXT@" +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") +config.host_triple = "@LLVM_HOST_TRIPLE@" +config.target_triple = "@TARGET_TRIPLE@" +config.host_arch = "@HOST_ARCH@" + +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@" + + at LIT_SITE_CFG_IN_FOOTER@ + +# Let the main config do the real work. +lit_config.load_config(config, "@DEBUGINFO_TESTS_SO...

...; >> +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" >> +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" >> +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") >> +config.host_triple = "@LLVM_HOST_TRIPLE@" >> +config.target_triple = "@TARGET_TRIPLE@" >> +config.host_arch = "@HOST_ARCH@" >> + >> +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@" >> + >> + at LIT_SITE_CFG_IN_FOOTER@ >> + >> +# Let the main config do...

...PLUGIN_EXT@" > +config.debuginfo_tests_obj_root = "@DEBUGINFO_TESTS_BINARY_DIR@" > +config.debuginfo_tests_src_root = "@DEBUGINFO_TESTS_SOURCE_DIR@" > +config.has_lld = lit.util.pythonize_bool("@DEBUGINFO_TESTS_HAS_LLD@") > +config.host_triple = "@LLVM_HOST_TRIPLE@" > +config.target_triple = "@TARGET_TRIPLE@" > +config.host_arch = "@HOST_ARCH@" > + > +config.llvm_use_sanitizer = "@LLVM_USE_SANITIZER@" > + > + at LIT_SITE_CFG_IN_FOOTER@ > + > +# Let the main config do the real work. > +lit_config....

On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote: [ brutal-snip ] ... > [ TODO#S: Before doing a 2nd build (and in a 3rd run using more > optimized binaries) ] > > How do I anable LTO via CMAKE? > > > LLVM_ENALBLE_LTO=On > [ v4 of my build-script attached ] Hi Chris, thanks for the response! That seems to work (see below). $ cd

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

Trying to run a self host "ninja check-clang" with ASan enabled I hit a /lot/ of errors like this (strangely I hit none of these in check-llvm, only in check-clang): Any ideas? ==10525==ERROR: AddressSanitizer failed to deallocate 0x10800 (67584) bytes at address 0x631000014800 ==10525==AddressSanitizer CHECK failed:

...Path to llgo source directory LLVM_EXTERNAL_LLGO_SOURCE_DIR:PATH= //Path to parallel-libs source directory LLVM_EXTERNAL_PARALLEL_LIBS_SOURCE_DIR:PATH= //Set to ON to force using an old, unsupported host toolchain. LLVM_FORCE_USE_OLD_HOST_TOOLCHAIN:BOOL=OFF //Host on which LLVM binaries will run LLVM_HOST_TRIPLE:STRING=x86_64-unknown-linux-gnu //Generate build targets for llvm documentation. LLVM_INCLUDE_DOCS:BOOL=ON //Generate build targets for the LLVM examples LLVM_INCLUDE_EXAMPLES:BOOL=ON //Include the Go bindings tests in test build targets. LLVM_INCLUDE_GO_TESTS:BOOL=OFF //Generate build targets...