similar to: Enable compiler warnings

Hello, I'm working on a project involving LLVM and keep shifting between the Debug and Release build by assigning different values to CMAKE_BUILD_TYPE in <llvm_build>/CMakeCache.txt and then building it. I wanted to know if this was a safe alternative to re-configuring the build after removing <llvm_build>/CMakeFiles/ and <llvm_build>/CMakeCache.txt. Thanks, Sanjay

On Sat, Oct 14, 2017 at 4:22 PM, Don Hinton <hintonda at gmail.com> wrote: > Hi Jack: > > The only way I could reproduce the problem you are seeing was to rerun > cmake with -DCMAKE_BUILD_TYPE=Debug in a build directory previously > configured with -DCMAKE_BUILD_TYPE=Release. I can fix that, but not sure > if it's what you are seeing. > > If this isn't your

On Sat, Oct 14, 2017 at 11:38 AM, Don Hinton <hintonda at gmail.com> wrote: > Sorry, LLVM_FORCE_ENABLE_DUMP is the variable, which is used along with > LLVM_ENABLE_ASSERTIONS to set LLVM_ENABLE_DUMP. > > Again, I'm working on a fix, but could you also provide your cmake > command? Looks like we aren't handling your use case correctly. > > thanks.. > don >

Hi, I see the following variables in the CMakeCache.txt: SANITIZER_CXX_ABI:STRING=default //STRINGS property for variable: SANITIZER_CXX_ABI SANITIZER_CXX_ABI-STRINGS:INTERNAL=none;default;libcxxabi;libstdc++ Regards, ismail On Tue, Aug 1, 2017 at 7:32 PM, Vedant Kumar <vsk at apple.com> wrote: > >> On Aug 1, 2017, at 7:07 AM, İsmail Dönmez via llvm-dev <llvm-dev at

If I've configured a Release build, build it and then go back and re-run cmake with -DCMAKE_BUILD_TYPE=Debug (and nothing else changed), almost nothing gets rebuilt when I try to build. Is this expected? I know I can edit CMakeCache.txt directly and trigger an essentially full rebuild. -David

On Sat, Oct 14, 2017 at 11:25 AM, Don Hinton <hintonda at gmail.com> wrote: > Hi Jack: > > Yes, I was just looking at that. Seems like TableGen wasn't done along > with the rest of llvm. I'll work up a complete patch shortly. > > Btw, I'm curious how this happened. Do you have a stale CMakeCache.txt by > any chance? You might check the value for

Also please note that there is a description of each option in the CMakeLists.txt :) llvm/trunk/CMakeLists.txt option(LLVM_ENABLE_MODULES "Compile with C++ modules enabled." OFF) option(LLVM_ENABLE_CXX1Y "Compile with C++1y enabled." OFF) option(LLVM_ENABLE_LIBCXX "Use libc++ if available." OFF) option(LLVM_ENABLE_LIBCXXABI "Use libc++abi when using

While doing a make on the recently checkout version: I got the following errors: [ 68%] Built target dd [ 68%] Built target compiler-rt-headers [ 68%] Building C object projects/compiler-rt/lib/builtins/CMakeFiles/clang_rt.builtins-x86_64.dir/x86_64/floatdidf.c.o In file included from /home/tthtlc/llvm/llvm/projects/compiler-rt/lib/builtins/x86_64/floatdidf.c:9:0:

On Tue, Dec 20, 2016 at 5:05 PM, Teresa Johnson <tejohnson at google.com> wrote: > Hi Carsten, > > A few responses below, but first, can you get the link command for > lldb.so.3.9.1? Last time it was the lldb.so build that was using > ld.bfd with the gold plugin which was exposing this issue. Where would I find it in an otherwise already terminated process? > On Tue, Dec

I configured with this command: " cmake ../llvm -G"Visual Studio 16 2019" -A Win32 -Thost=x64 -DLLVM_ENABLE_EH=ON -DCMAKE_BUILD_TYPE=Release -DLLVM_USE_CRT_RELEASE=MT -DLLVM_ENABLE_RTTI=ON -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;lld;libcxx;libcxxabi" -DCMAKE_CXX_FLAGS="/permissive- /D_SILENCE_ALL_CXX17_DEPRECATION_WARNINGS" -DCMAKE_CXX_STANDARD=17 "

Just posted this fix on ninja's github page, but figured I'd share it with a larger audience. Every time I run cmake && ninja in a new build directory, ninja will rerun cmake because the entry for build.ninja in .ninja_log is older than the timestamp on CMakeCache.txt, even if the timestamps on the actual file isn't older. The following patch fixes the problem, i.e.,

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

Hi Carsten, A few responses below, but first, can you get the link command for lldb.so.3.9.1? Last time it was the lldb.so build that was using ld.bfd with the gold plugin which was exposing this issue. On Tue, Dec 20, 2016 at 5:49 AM, Carsten Mattner <carstenmattner at gmail.com> wrote: > ​Hi again, Teresa. > > Looks like I had forgotten to report back with success > when

George Karpenkov <ekarpenkov at apple.com> writes: > Should -DCMAKE_CXX_COMPILER be also specified? CMake is smart enough to infer that from C_COMPILER: % grep CMAKE_CXX_COMPILER CMakeCache.txt CMAKE_CXX_COMPILER:FILEPATH=/Users/bogner/llvm-lkgc/bin/clang++ >> On Aug 24, 2017, at 11:29 AM, Justin Bogner <mail at justinbogner.com> wrote: >> >> (kcc, george:

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

>> Now I'm using LLVM_BUILD_EXAMPLES=OFF and I have >> >> //Build LLVM example programs. >> LLVM_BUILD_EXAMPLES:BOOL=OFF >> >> in the cmakecache.txt file but it also does not seem to >> work. >> > > What that means? LLVM_BUILD_EXAMPLES shall create build targets for the > examples but do not build them when you build the ALL_BUILD

There is a second issue with the new TableGenBackendSkeleton.cpp file. It is a skeleton file for writing a new TableGen backend. /home/buildbots/docker-RHEL-buildbot/SetupBot/worker_env/ppc64le-clang-rhel-test/clang-ppc64le-rhel/llvm/llvm/lib/TableGen/TableGenBackendSkeleton.cpp:38:17: error: private field 'Records' is not used [-Werror,-Wunused-private-field] RecordKeeper &Records;

> Which combination of cmake/ninja versions are you using (latest are > v3.4.3 and v1.6.0)? > With this combination I could reduce build-time down from approx. 3h down to 01h20m. $ egrep -i 'jobs|ninja' llvm-build/CMakeCache.txt //Program used to build from build.ninja files. CMAKE_MAKE_PROGRAM:FILEPATH=/opt/cmake/bin/ninja //Define the maximum number of concurrent compilation

Now that I can build LLVM on Windows, I tried doing it. -------------------------- ... some good stuff ... C:/LLVM/llvm-project/llvm/lib/Support/Chrono.cpp:35:17: error: '::localtime_s' has not been declared; did you mean 'localtime'? 35 | int Error = ::localtime_s(&Storage, &OurTime); | ^~~~~~~~~~~ | localtime (The error

On Thu, Mar 9, 2017 at 3:00 PM Chris Bieneman <beanz at apple.com> wrote: > I'll try and reproduce later today. Is this Linux? Can you give me your > CMake command line? > Excuse the delay, been busy setting up a new machine - also an opportunity to try clean cmake setups rather than my aging configurations that have a bunch of old stuff baked in and manual variables changed,