search for: llvm_enable_timestamps

Hello LLVM-Dev, Today if a user checks out LLVM, configures with no options specified, and builds the result is non-deterministic. Meaning if you clean and build again the binaries are not identical. This impacts all target platforms equally and is caused by the default value of LLVM_ENABLE_TIMESTAMPS being On. I believe this is incorrect behavior, and I’m curious what the wider community thinks. It is my belief that the default LLVM configuration (meaning no options specified) should be deterministic, and that any option in our build/configuration system that can impact determinism should be...

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

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:

...un time type information LLVM_ENABLE_RTTI:BOOL=ON //Use Sphinx to generate llvm documentation. LLVM_ENABLE_SPHINX:BOOL=OFF //Use terminfo database if available. LLVM_ENABLE_TERMINFO:BOOL=ON //Use threads if available. LLVM_ENABLE_THREADS:BOOL=ON //Enable embedding timestamp information in build LLVM_ENABLE_TIMESTAMPS:BOOL=ON //Enable compiler warnings. LLVM_ENABLE_WARNINGS:BOOL=ON //Fail and stop if a warning is triggered. LLVM_ENABLE_WERROR:BOOL=1 //Use zlib for compression/decompression if available. LLVM_ENABLE_ZLIB:BOOL=ON //Semicolon-separated list of experimental targets to build. LLVM_EXPERIMENTAL_TA...