search for: llvm_build_global_isel

Hi all, Now, four backends (if I am counting right: X86, ARM, AArch64, AMDGPU) are working on bringing-up GlobalISel, I’d like to switch the default of the LLVM_BUILD_GLOBAL_ISEL variable in CMake, such that the framework gets built by default. ** Impact of Flipping the Switch ** * Upsides * For people developing on GlobalISel, it will: - Simplify the CMake command to type :) - Build/Test GlobalISel on all the LLVM bots For people not developing on GlobalISel, it will:...

...lists.llvm.org> wrote: > > On 14 January 2017 at 01:54, Quentin Colombet via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Now, four backends (if I am counting right: X86, ARM, AArch64, AMDGPU) are working on bringing-up GlobalISel, I’d like to switch the default of the LLVM_BUILD_GLOBAL_ISEL variable in CMake, such that the framework gets built by default. > > Hi Quentin, > > I'm not extremely confident in a full switch right now, mainly due to > Michael's concerns. The ARM port is in its initial stage and there > could still be many refactorings and destruc...

...7 at 5:54 PM, Quentin Colombet via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > Hi all, > > Now, four backends (if I am counting right: X86, ARM, AArch64, AMDGPU) are working on bringing-up GlobalISel, I’d like to switch the default of the LLVM_BUILD_GLOBAL_ISEL variable in CMake, such that the framework gets built by default. > > ** Impact of Flipping the Switch ** > > * Upsides * > > For people developing on GlobalISel, it will: > - Simplify the CMake command to type :) > - Build/Test GlobalISel on all the LLVM bots > >...

...GlobalISel (which also includes Linaro) will have a lot less work. But there's a cost to be paid, and that cost is a lot higher on the ARM/AArch64 side than x86, just because most developers use an x86 as their main machine. > Still, as a strawman proposal - would it make sense to add > LLVM_BUILD_GLOBAL_ISEL_EXPERIMENTAL, or something of that sort? The more > mature ports will build under LLVM_BUILD_GLOBAL_ISEL (which will be enabled > by default), the less mature ones only under > LLVM_BUILD_GLOBAL_ISEL_EXPERIMENTAL (which won't be), and moving a port from > GLOBAL_ISEL_EXPERIMENTAL to...

...des Linaro) will have a lot less work. But there's a cost to be > paid, and that cost is a lot higher on the ARM/AArch64 side than x86, > just because most developers use an x86 as their main machine. > > > > Still, as a strawman proposal - would it make sense to add > > LLVM_BUILD_GLOBAL_ISEL_EXPERIMENTAL, or something of that sort? The more > > mature ports will build under LLVM_BUILD_GLOBAL_ISEL (which will be > enabled > > by default), the less mature ones only under > > LLVM_BUILD_GLOBAL_ISEL_EXPERIMENTAL (which won't be), and moving a port > from > &g...

...t less work. But there's a cost to be >> paid, and that cost is a lot higher on the ARM/AArch64 side than x86, >> just because most developers use an x86 as their main machine. >> >> >> > Still, as a strawman proposal - would it make sense to add >> > LLVM_BUILD_GLOBAL_ISEL_EXPERIMENTAL, or something of that sort? The more >> > mature ports will build under LLVM_BUILD_GLOBAL_ISEL (which will be enabled >> > by default), the less mature ones only under >> > LLVM_BUILD_GLOBAL_ISEL_EXPERIMENTAL (which won't be), and moving a port from >&...

...39;s a cost to be >>> paid, and that cost is a lot higher on the ARM/AArch64 side than x86, >>> just because most developers use an x86 as their main machine. >>> >>> >>> > Still, as a strawman proposal - would it make sense to add >>> > LLVM_BUILD_GLOBAL_ISEL_EXPERIMENTAL, or something of that sort? The more >>> > mature ports will build under LLVM_BUILD_GLOBAL_ISEL (which will be enabled >>> > by default), the less mature ones only under >>> > LLVM_BUILD_GLOBAL_ISEL_EXPERIMENTAL (which won't be), and moving a por...

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:

..._32_BITS:BOOL=OFF //Build the llvm documentation. LLVM_BUILD_DOCS:BOOL=OFF //Build the LLVM example programs. If OFF, just generate build // targets. LLVM_BUILD_EXAMPLES:BOOL=ON //Build compiler-rt as an external project. LLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=OFF //Experimental: Build GlobalISel LLVM_BUILD_GLOBAL_ISEL:BOOL=ON //Build LLVM and tools with PGO instrumentation (experimental) LLVM_BUILD_INSTRUMENTED:BOOL=OFF //Build LLVM and tools with Code Coverage instrumentation (experimental) LLVM_BUILD_INSTRUMENTED_COVERAGE:BOOL=OFF //Build libllvm-c re-export library (Darwin Only) LLVM_BUILD_LLVM_C_DYLIB:BOO...