search for: minsizerel

...hough just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built clang and clang++ via gcc-4.6.3 under /usr/local/bin... /clang .../clang++ as follows: > mdriftmeyer at horus:~/DeveloperProjects/LLVMProject/cmake-llvm$ cmake > -DCMAKE_BUILD_TYPE=MinSizeRel > -DCMAKE_CXX_COMPILER=/usr/local/bin/clang++ > -DCMAKE_C_COMPILER=/usr/local/bin/clang -DCMAKE_CXX_FLAGS='-O2' > CMAKE_C_FLAGS='-O2' -DLLVM_BUILD_EXAMPLES=ON -DLLVM_BUILD_TESTS=ON > -DLLVM_INCLUDE_TESTS=ON > -DLLVM_TARGETS_TO_BUILD='ARM;CppBackend;PTX;Hexago...

...SCV (experimental) target. I noticed that the instructions on the wiki were out of dat because they said to use '-DLLVM_TARGETS_TO_BUILD', but this gave a warning to use `LLVM_EXPERIMENTAL_TARGETS_TO_BUILD` as well (or instead?). So I compiled with these options: cmake -DCMAKE_BUILD_TYPE=MinSizeRel -DCMAKE_C_COMPILER=gcc > -DCMAKE_CXX_COMPILER=g++ -DCMAKE_INSTALL_PREFIX=../install > -DLLVM_OPTIMIZED_TABLEGEN=On -LLVM_EXPERIMENTAL_TARGETS_TO_BUILD="RISCV" > -DLLVM_TARGETS_TO_BULD="RISCV" .. > However after completing that compilation I get this message: CMake...

...> Hi Adrian > > I’m not sure if the CMAKE_CXX_FLAGS is used in LLVM. We have our own > flags for different configurations. I don’t remember if our ones inherit > from CMAKE_CXX_FLAGS or override it completely. Anyway, they are: > - CMAKE_CXX_FLAGS_DEBUG > - CMAKE_CXX_FLAGS_MINSIZEREL > - CMAKE_CXX_FLAGS_RELEASE > - CMAKE_CXX_FLAGS_RELWITHDEBINFO > > The one of those you get depends on what you set CMAKE_BUILD_TYPE to. > Options are ‘Debug, Release, RelWithDebInfo, MinSizeRel’ > > Cheers, > Pete > > On Jul 17, 2015, at 8:41 PM, adek at adek.io wr...

...e > recently: > > From: José Fonseca > Subject: [PATCH]: MSVC build enhancements > Date: Sat, 6 Mar 2010 10:43:50 +0000 > > I've read this thread but what I propose is simpler because this only allows the user to choose static runtime for all configurations (Debug, Release, MinSizeRel and RelWithDebInfo). I understand that it is not ideal because one would normally want MTd for Debug and MT for the rest but that's how it works now for MD as well. This patch doesn't try to solve this issue. But I don't see why static runtime options should be excluded as they are now....

...: José Fonseca >> Subject: [PATCH]: MSVC build enhancements >> Date: Sat, 6 Mar 2010 10:43:50 +0000 >> >> > I've read this thread but what I propose is simpler because this only allows > the user to choose static runtime for all configurations (Debug, Release, > MinSizeRel and RelWithDebInfo). I understand that it is not ideal because > one would normally want MTd for Debug and MT for the rest but that's how it > works now for MD as well. This patch doesn't try to solve this issue. But I > don't see why static runtime options should be excluded a...

...>> I’m not sure if the CMAKE_CXX_FLAGS is used in LLVM. We have our own >> flags for different configurations. I don’t remember if our ones >> inherit from CMAKE_CXX_FLAGS or override it completely. Anyway, they are: >> - CMAKE_CXX_FLAGS_DEBUG >> - CMAKE_CXX_FLAGS_MINSIZEREL >> - CMAKE_CXX_FLAGS_RELEASE >> - CMAKE_CXX_FLAGS_RELWITHDEBINFO >> >> The one of those you get depends on what you set CMAKE_BUILD_TYPE to. >> Options are ‘Debug, Release, RelWithDebInfo, MinSizeRel’ >> >> Cheers, >> Pete >>> On Jul 17, 2...

'-DCMAKE_CXX_FLAGS=-fno-omit-frame-pointer -Wno-maybe-uninitialized -fPIC -fPIE' -- The C compiler identification is GNU 4.8.1 -- The CXX compiler identification is GNU 4.8.1 -- Check for working C compiler: /home/engshare/third-party2/gcc/4.8.1/centos6-native/cc6c9dc/bin/gcc -- Check for working C compiler: /home/engshare/third-party2/gcc/4.8.1/centos6-native/cc6c9dc/bin/gcc -- works --

On 11 July 2015 at 13:14, Caldarale, Charles R <Chuck.Caldarale at unisys.com> wrote: >> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] >> On Behalf Of Dibyendu Majumdar >> Subject: [LLVMdev] JIT compilation 2-3 times slower in latest LLVM snapshot > >> I updated my clone of the LLVM github mirror today and I am finding >> that

...in' option // for the GCC compiler CMAKE_C_COMPILER_RANLIB:FILEPATH=C:/MinGW/bin/gcc-ranlib.exe //Flags used by the C compiler during all build types. CMAKE_C_FLAGS:STRING= //Flags used by the C compiler during DEBUG builds. CMAKE_C_FLAGS_DEBUG:STRING=-g //Flags used by the C compiler during MINSIZEREL builds. CMAKE_C_FLAGS_MINSIZEREL:STRING=-Os -DNDEBUG //Flags used by the C compiler during RELEASE builds. CMAKE_C_FLAGS_RELEASE:STRING=-O3 -DNDEBUG //Flags used by the C compiler during RELWITHDEBINFO builds. CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=-O2 -g -DNDEBUG -----------------------------------...

...LAGS is used in LLVM. We have our own > > >> flags for different configurations. I don’t remember if our ones > > >> inherit from CMAKE_CXX_FLAGS or override it completely. Anyway, they are: > > >> - CMAKE_CXX_FLAGS_DEBUG > > >> - CMAKE_CXX_FLAGS_MINSIZEREL > > >> - CMAKE_CXX_FLAGS_RELEASE > > >> - CMAKE_CXX_FLAGS_RELWITHDEBINFO > > >> > > >> The one of those you get depends on what you set CMAKE_BUILD_TYPE to. > > >> Options are ‘Debug, Release, RelWithDebInfo, MinSizeRel’ > > >&g...

> Try checking out libcxxabi as well. It helped, thanks. But I have another problem now. Regression tests don't pass: http://paste.ubuntu.com/15406485/ Also I discovered that build process sometimes consumes about 10 Gb of RAM. Luckily I have total 16 Gb of RAM. Still I had to close Google Chrome and kill KVM guest systems to compile a project. I think its just an insanity. -- Best

...ATCH]: MSVC build enhancements > >> Date: Sat, 6 Mar 2010 10:43:50 +0000 > >> > >> > > I've read this thread but what I propose is simpler because this only > allows > > the user to choose static runtime for all configurations (Debug, Release, > > MinSizeRel and RelWithDebInfo). I understand that it is not ideal because > > one would normally want MTd for Debug and MT for the rest but that's how > it > > works now for MD as well. This patch doesn't try to solve this issue. But > I > > don't see why static runtime opt...

Victor Zverovich <victor.zverovich at googlemail.com> writes: > Hi llvm-dev, > > Attached are two patches for the LLVM cmake build system. > > The first one adds static runtimes (MT and MTd) to the list of runtimes for > the MSVC build. This seems not to be as easy as you put it. It was discussed here recently: From: José Fonseca Subject: [PATCH]: MSVC build enhancements

...-- Threads enabled. > -- Doxygen disabled. > -- Sphinx disabled. > -- Go bindings disabled. > -- Could NOT find OCaml (missing: OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH) > -- OCaml bindings disabled. > -- Using Debug VC++ CRT: MDd > -- Using Release VC++ CRT: MD > -- Using MinSizeRel VC++ CRT: MD > -- Using RelWithDebInfo VC++ CRT: MD > -- Using Release VC++ CRT: MD > -- Constructing LLVMBuild project information > -- LLVMHello ignored -- Loadable modules not supported on this platform. > -- Targeting X86 > -- BugpointPasses ignored -- Loadable modules not sup...

Hi llvm-dev, Attached are two patches for the LLVM cmake build system. The first one adds static runtimes (MT and MTd) to the list of runtimes for the MSVC build. The second one makes it possible to use llvm_config in external projects. In this patch I took the liberty of changing the format of LLVMLibDeps.cmake to define a single variable LLVM_LIB_DEPS instead of MSVC_LIB_DEPS_*.

Hi, The Object/nm-archive test is failing for me on 64-bit Windows. It started recently, possibly with r166767. The output is as follows: 12> ******************** TEST 'LLVM :: Object/nm-archive.test' FAILED ******************** 12> Script: 12> -- 12> C:/dev/llvm/build/bin/Debug/llvm-nm.EXE c:\dev\llvm\test\Object/Inputs/archive-test.a-coff-i386 |

Hi, I'm trying to do a build and install on Windows 10 with Visual Studio 2015 Community Edition for the X86 and ARM targets, from the current release_40 branch. While compilation completes without error, the INSTALL target fails with the following error: 54> CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:34 (file): 54> file INSTALL cannot find 54>

...gt; Could NOT find Python module pygments.lexers.c_cpp > > Could NOT find Python module yaml > > LLVM host triple: x86_64-pc-windows-msvc > > LLVM default target triple: x86_64-pc-windows-msvc > > Using Debug VC++ CRT: MDd > > Using Release VC++ CRT: MD > > Using MinSizeRel VC++ CRT: MD > > Using RelWithDebInfo VC++ CRT: MD > > Constructing LLVMBuild project information > > CMake Error at C:/Program > Files/CMake/share/cmake-3.13/Modules/FindSubversion.cmake:123 (message): > Command "C:/Program Files/TortoiseSVN/bin/ info C:/llvm" fai...

...indings disabled. Could NOT find Python module pygments Could NOT find Python module pygments.lexers.c_cpp Could NOT find Python module yaml LLVM host triple: x86_64-pc-windows-msvc LLVM default target triple: x86_64-pc-windows-msvc Using Debug VC++ CRT: MDd Using Release VC++ CRT: MD Using MinSizeRel VC++ CRT: MD Using RelWithDebInfo VC++ CRT: MD Constructing LLVMBuild project information CMake Error at C:/Program Files/CMake/share/cmake-3.13/Modules/FindSubversion.cmake:123 (message): Command "C:/Program Files/TortoiseSVN/bin/ info C:/llvm" failed with output: Call Stack (most re...

I probably need GCC for Git bash. And the one I have is MinGW's GCC, which is the one for Windows. I don't know why CMake is trying to find Linux headers. Hopefully someone who knows better what to do will weigh in here. @Jonathan Goodwin<mailto:jondgoodwin at gmail.com> , are you sure you didn't have to tell it where the header files for Windows are? If I need to specify