search for: dllvm_enable_lto

I tried building llvm, clang, lld, lldb from the 3.9 svn release branch with LTO, and some of the results were unexpected. I first tried to rebuild llvm with llvm-3.9, which has ThinLTO, by providing -DLLVM_ENABLE_LTO=Thin, but that failed very quickly, so I fell back to building with -DLLVM_ENABLE_LTO=On and using the system CC/CXX (gcc 6.1). The resulting installed build is many times bigger than the non-LTO version. Is this to be expected? I thought LTO would reduce size by detecting more unused code. The b...

On Fri, Sep 16, 2016 at 10:18 PM, Teresa Johnson <tejohnson at google.com> wrote: > > Cc'ing llvm-dev again in case someone knows what is going on. > > That error is coming from a polly configure script, which I don't > have cloned into my own tree. Not sure why polly would behave > differently when configuring for ThinLTO. Does polly configure ok > when

...ev <llvm-dev at lists.llvm.org> wrote: >> >> I tried building llvm, clang, lld, lldb from the 3.9 svn release >> branch with LTO, and some of the results were unexpected. >> >> I first tried to rebuild llvm with llvm-3.9, which has ThinLTO, by >> providing -DLLVM_ENABLE_LTO=Thin, but that failed very quickly, so I >> fell back to building with -DLLVM_ENABLE_LTO=On and using the system >> CC/CXX (gcc 6.1). >> >> The resulting installed build is many times bigger than the non-LTO >> version. Is this to be expected? I thought LTO would reduc...

...LER=/path/to/release_build/bin/clang++ \ -DCMAKE_C_COMPILER=/path/to/release_build/bin/clang \ -DLLVM_USE_LINKER=/path/to/release_build/bin/ld.lld \ -DLLVM_CCACHE_BUILD=ON \ -DLLVM_BUILD_INSTRUMENTED=IR \ -DLLVM_BUILD_RUNTIME=No \ -DLLVM_ENABLE_ZLIB=1 \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_ENABLE_LTO=Thin \ -DCMAKE_RANLIB=/path/to/release_build/bin/llvm-ranlib \ -DCMAKE_AR=/path/to/release_build/bin/llvm-ar I tried this without specifying zlib being enabled, without thinlto, everything I could come up with really. * Built a debug Clang with the following configuration: cmake -G Ninja ../l...

...path/to/release_build/bin/clang \ >> -DLLVM_USE_LINKER=/path/to/release_build/bin/ld.lld \ >> -DLLVM_CCACHE_BUILD=ON \ >> -DLLVM_BUILD_INSTRUMENTED=IR \ >> -DLLVM_BUILD_RUNTIME=No \ >> -DLLVM_ENABLE_ZLIB=1 \ >> -DCMAKE_BUILD_TYPE=Release \ >> -DLLVM_ENABLE_LTO=Thin \ >> -DCMAKE_RANLIB=/path/to/release_build/bin/llvm-ranlib \ >> -DCMAKE_AR=/path/to/release_build/bin/llvm-ar >> >> I tried this without specifying zlib being enabled, without thinlto, >> everything I could come up with really. >> >> * Built a debu...

where should the file build_llvm_package.bat be placed and how should the build_llvm_package.bat be called? or is there a another way to do a two stage build of the llvm project on windows starting with using visual studio 2017 community. -------------- next part -------------- An HTML attachment was scrubbed... URL:

The configuration we’re mentioning is a 2-stage bootstrap: You need first to build without LTO your own clang, and then use it for the LTO build. — Mehid > On Sep 20, 2016, at 10:17 AM, Michael Kruse <llvmdev at meinersbur.de> wrote: > > I am the author of Polly's/ISL's platform tests and could reproduce > the problem on my system with this error message: > >

...visible > in the error trace below: What is your exact cmake invocation? I don’t think cmake accept “LDFLAGS” directly, instead it is using “CMAKE_MODULE_LINKER_FLAGS”, “CMAKE_SHARED_LINKER_FLAGS”, and “CMAKE_EXE_LINKER_FLAGS”. Ideally these would be set automatically when building LLVM with -DLLVM_ENABLE_LTO=THIN. Teresa, I think it would be valuable to update llvm/cmake/modules/HandleLLVMOptions.cmake and make sure 1) either LLD or GOLD is used, 2) add the relevant plugin flags if needed. if(uppercase_LLVM_ENABLE_LTO STREQUAL "THIN") append("-flto=thin" CMAKE_CXX_FLAGS CMAKE_...

...E}/clang/toInstall \ -DLLVM_TABLEGEN=${MYHOSTBIN}/llvm-tblgen \ -DCLANG_TABLEGEN=${MYHOSTBIN}/clang-tblgen \ -DLLVM_DEFAULT_TARGET_TRIPLE=arm-none-eabi \ -DLLVM_TARGET_ARCH=ARM \ -DLLVM_TARGETS_TO_BUILD=ARM \ -DLLVM_ENABLE_LTO=Full \ -DCMAKE_C_FLAGS="${MYCFLAGS}" \ -DCMAKE_CXX_FLAGS="${MYCFLAGS}" \ -DCMAKE_SYSROOT=${MYGNUARM_ROOT} \ -DCMAKE_TOOLCHAIN_FILE=../toolchain.txt \ -DCMAKE_C_COMPILER=${MYGNUARM_ROOT}/bin/arm-none-eabi-...

...FF \ > -DLLVM_BUILD_TESTS=OFF \ > -DLLVM_INCLUDE_TESTS=OFF \ > -DLLVM_BUILD_DOCS=OFF \ > -DLLVM_INCLUDE_DOCS=OFF \ > -DLLVM_ENABLE_DOXYGEN=OFF \ > -DLLVM_ENABLE_SPHINX=OFF \ > -DLLDB_DISABLE_PYTHON=ON \ > -DCLANG_PLUGIN_SUPPORT=OFF \ > -DLLVM_ENABLE_LTO=Thin \ > -DCMAKE_AR=$PREFIX/bin/llvm-ar \ > -DCMAKE_RANLIB=$PREFIX/bin/llvm-ranlib > > $ ninja -j4 > /usr/bin/ld: error: Could not create temporary file: Too many open files > ThinLTO needs to create as many temporary files as there are input modules to the link. From you...

On Tue, Sep 27, 2016 at 6:53 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > > > On Sep 27, 2016, at 2:18 AM, Carsten Mattner <carstenmattner at gmail.com> > wrote: > > > >> On Mon, Sep 26, 2016 at 11:02 PM, Teresa Johnson <tejohnson at google.com> > wrote: > >> I'll either need to get a reproducer from you and/or try to repro

Hello everyone, I'm trying to compile LLVM and Clang into LLVM IR with debug info. I know that clang++ -g2 -S -emit-llvm <filename> does this, but I'm unfamiliar with CMake. I tried changing CMAKE_CXX_FLAGS in CMakeCache.txt to "clang++ -g2 -S -emit-llvm," "-g2 -S -emit-llvm," and "-emit-llvm," but everything I tried resulted in a failed build, and/or

...including: cmake -G "Visual Studio 15 2017" -A x64 -T"llvm",host=x64 -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" -DLLVM_ENABLE_LTO=true -DLLVM_ENABLE_PDB=true -DLLVM_ENABLE_PROJECTS=lld ../llvm but it seems like the generator overrides it. ps: Created a phabricator account On Mon, Feb 25, 2019 at 2:48 PM Alexandre Ganea <alexandre.ganea at ubisoft.com> wrote: > > That's good news. For having debug info, yo...

...;Visual Studio 15 2017" -A x64 -T"llvm",host=x64 -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" >> -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" >> -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" >> -DLLVM_ENABLE_LTO=true -DLLVM_ENABLE_PDB=true -DLLVM_ENABLE_PROJECTS=lld ../llvm >> >> but it seems like the generator overrides it. >> >> >> ps: Created a phabricator account >> >> On Mon, Feb 25, 2019 at 2:48 PM Alexandre Ganea <alexandre.ganea at ubisoft.com> wrote...

...15 2017" -A x64 -T"llvm",host=x64 -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" > >> -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > >> -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > >> -DLLVM_ENABLE_LTO=true -DLLVM_ENABLE_PDB=true -DLLVM_ENABLE_PROJECTS=lld ../llvm > >> > >> but it seems like the generator overrides it. > >> > >> > >> ps: Created a phabricator account > >> > >> On Mon, Feb 25, 2019 at 2:48 PM Alexandre Ganea <alexa...

...;Visual Studio 15 2017" -A x64 -T"llvm",host=x64 -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" >> -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" >> -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" >> -DLLVM_ENABLE_LTO=true -DLLVM_ENABLE_PDB=true -DLLVM_ENABLE_PROJECTS=lld ../llvm >> >> but it seems like the generator overrides it. >> >> >> ps: Created a phabricator account >> >> On Mon, Feb 25, 2019 at 2:48 PM Alexandre Ganea <alexandre.ganea at ubisoft.com<mailto...

...A x64 -T"llvm",host=x64 -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" > > >> -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > >> -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > >> -DLLVM_ENABLE_LTO=true -DLLVM_ENABLE_PDB=true > > >> -DLLVM_ENABLE_PROJECTS=lld ../llvm > > >> > > >> but it seems like the generator overrides it. > > >> > > >> > > >> ps: Created a phabricator account > > >> > > >> On...

...fully disambiguate all may-aliasing memory accesses no matter how many runtime checks are required. [r259610](http://reviews.llvm.org/rL259610). * The way bitsets are used to encode type information has now been documented. [r259619](http://reviews.llvm.org/rL259619). * You can now use the flag `-DLLVM_ENABLE_LTO` with CMake to build LLVM with link-time optimisation. [r259766](http://reviews.llvm.org/rL259766). * TableGen's AsmOperandClass gained the `IsOptional` field. Setting this to 1 means the operand is optional and the AsmParser will not emit an error if the operand isn't present. [r259913](h...

That's good news. For having debug info, you could try adding /Z7 on the cmake cmd-line, such as -DCMAKE_CXX_FLAGS="/Z7". Or use the 'RelWithDebInfo' target instead of 'Release' and add -DCMAKE_CXX_FLAGS="/Ob2" (because that target uses /Ob1 as a default). Can you please send a patch on Phabricator if you fix the LLVM_ENABLE_PDB issue with Clang? The goal

...gt; -DCMAKE_LINKER="C:/Program Files/LLVM/bin/lld-link.exe" > > > > >> -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > > > >> -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang-cl.exe" > > > > >> -DLLVM_ENABLE_LTO=true -DLLVM_ENABLE_PDB=true > > > > >> -DLLVM_ENABLE_PROJECTS=lld ../llvm > > > > >> > > > > >> but it seems like the generator overrides it. > > > > >> > > > > >> > > > > >> ps: Created a p...