search for: dllvm_polly_link_into_tools

...urce tree as well). Neither "make LLVMPolly -j8" nor "make Polly -j8" resulted in an error on a clean build. Can you try "make intrinsics_gen" before building anything else? The should generate the missing "llvm/IR/Attributes.gen". You could also try "-DLLVM_POLLY_LINK_INTO_TOOLS=OFF". Michael

...CMAKE_C_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_CXX_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" -DCMAKE_LINKER="%VS2019%/bin/HostX64/x64/link.EXE" -DLLVM_ENABLE_PROJECTS="llvm;clang;lld;clang-tools-extra;compiler-rt;mlir;polly" -DLLVM_ENABLE_PDB=ON -DLLVM_POLLY_LINK_INTO_TOOLS=ON These tests fail with Clang 9.0.1: Failing Tests (3): Clang Tools :: clang-tidy/checkers/cert-mem57-cpp-cpp17.cpp Clang Tools :: clang-tidy/checkers/performance-noexcept-move-constructor-fix.cpp Polly :: ScopInfo/memset_null.ll Expected Passes : 57727 Expected Failures : 2...

..." nor "make Polly -j8" >> resulted in an error on a clean build. >> >> Can you try "make intrinsics_gen" before building anything else? The >> should generate the missing "llvm/IR/Attributes.gen". >> >> You could also try "-DLLVM_POLLY_LINK_INTO_TOOLS=OFF". >> >> Michael > > Yes, my build proceeded after make intrinsics_gen. > > But originally I run make -j 4 for entire source tree (clean build), > not particular Polly target. In such proper solution is that Polly > should depend on intrinsics_gen. I try to di...

...HostX64/x64/cl.EXE" >> -DCMAKE_CXX_COMPILER="%VS2019%/bin/HostX64/x64/cl.EXE" >> -DCMAKE_LINKER="%VS2019%/bin/HostX64/x64/link.EXE" >> -DLLVM_ENABLE_PROJECTS="llvm;clang;lld;clang-tools-extra;compiler-rt;mlir;polly" >> -DLLVM_ENABLE_PDB=ON -DLLVM_POLLY_LINK_INTO_TOOLS=ON >> >> >> >> These tests fail with Clang 9.0.1: >> >> >> >> Failing Tests (3): >> >> Clang Tools :: clang-tidy/checkers/cert-mem57-cpp-cpp17.cpp >> >> Clang Tools :: >> clang-tidy/checkers/performance-noexcept-m...

...-m64 -I/usr/local/valgrind/include" \ -DCMAKE_CXX_COMPILER:STRING="/usr/local/gcc-5.3.0/bin/g++" \ -DCMAKE_CXX_FLAGS:STRING="-m64 -I/usr/local/valgrind/include" \ -DCMAKE_EXE_LINKER_FLAGS:STRING="-m64" \ -DLLVM_LIBDIR_SUFFIX:STRING="64" \ -DLLVM_POLLY_LINK_INTO_TOOLS:BOOL=ON \ -DLIBOMPTARGET_DEP_LIBELF_INCLUDE_DIR:STRING="/usr/local/elfutils-0.169/include" \ -DLIBOMPTARGET_DEP_LIBELF_LIBRARIES:STRING="/usr/local/elfutils-0.169/lib64/libelf.so" \ -DLIBOMPTARGET_DEP_LIBFFI_INCLUDE_DIR:STRING="/usr/include" \ -DLIBOMPTARGET...

Hi Eugene, It is strange, I also do a clean build with CMake+make with r301734 and it is ok. Could you provide more details? Thanks Hongbin On Mon, May 1, 2017 at 10:58 AM, Eugene Zelenko via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi, Michael! > > On Sun, Apr 30, 2017 at 2:06 PM, Michael Kruse <llvmdev at meinersbur.de> > wrote: > > 2017-04-29 0:49

...-m64 -I/usr/local/valgrind/include" \ -DCMAKE_CXX_COMPILER:STRING="/usr/local/gcc-5.3.0/bin/g++" \ -DCMAKE_CXX_FLAGS:STRING="-m64 -I/usr/local/valgrind/include" \ -DCMAKE_EXE_LINKER_FLAGS:STRING="-m64" \ -DLLVM_LIBDIR_SUFFIX:STRING="64" \ -DLLVM_POLLY_LINK_INTO_TOOLS:BOOL=ON \ -DLIBOMPTARGET_DEP_LIBELF_INCLUDE_DIR:STRING="/usr/local/elfutils-0.169/include" \ -DLIBOMPTARGET_DEP_LIBELF_LIBRARIES:STRING="/usr/local/elfutils-0.169/lib64/libelf.so" \ -DLIBOMPTARGET_DEP_LIBFFI_INCLUDE_DIR:STRING="/usr/include" \ -DLIBOMPTARGET...

...-m64 -I/usr/local/valgrind/include" \ -DCMAKE_CXX_COMPILER:STRING="/usr/local/gcc-6.4.0/bin/g++" \ -DCMAKE_CXX_FLAGS:STRING="-m64 -I/usr/local/valgrind/include" \ -DCMAKE_EXE_LINKER_FLAGS:STRING="-m64" \ -DLLVM_LIBDIR_SUFFIX:STRING="64" \ -DLLVM_POLLY_LINK_INTO_TOOLS:BOOL=ON \ -DLIBOMPTARGET_DEP_LIBELF_INCLUDE_DIR:STRING="/usr/local/elfutils-0.169/include" \ -DLIBOMPTARGET_DEP_LIBELF_LIBRARIES:STRING="/usr/local/elfutils-0.169/lib64/libelf.so" \ -DLIBOMPTARGET_DEP_LIBFFI_INCLUDE_DIR:STRING="/usr/include" \ -DLIBOMPTARGET...