search for: enable_expensive_checks

When I build LLVM with ENABLE_EXPENSIVE_CHECKS=1, make check fails: Running /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/dg.exp ... FAIL: /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/2007-05-14-InlineAsmCstCrash.ll Failed with signal(SIGABRT) at line 1 while running: llvm-as < /home/foad/svn/llvm-project/llvm/trunk/te...

Hi Jay, > When I build LLVM with ENABLE_EXPENSIVE_CHECKS=1, make check fails: > > Running /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/dg.exp ... > FAIL: /home/foad/svn/llvm-project/llvm/trunk/test/CodeGen/ARM/2007-05-14-InlineAsmCstCrash.ll > Failed with signal(SIGABRT) at line 1 > while running: llvm-as < > /home/foad/s...

...bit of a flaw in the plan. I suppose the solution is to switch to SmallVector whenever this might be a problem. I'm a bit concerned that any new &empty[0] problems that are introduced will go unnoticed. With GNU libstdc++ they aren't diagnosed unless you build with -D_GLIBCXX_DEBUG (or ENABLE_EXPENSIVE_CHECKS=1). For now I'm testing with ENABLE_EXPENSIVE_CHECKS=1, and it is indeed catching lots of errors! > (though it is safe for smallvector). DR 464 proposes a new data() method. I'd suggest implementing that in SmallVector, instead of relying on the relaxed checking in operator[](). http...

On May 14, 2009, at 4:56 AM, Jay Foad wrote: > 2009/4/1 Chris Lattner <clattner at apple.com>: >> As far API design goes, we're in a mixed state. I'd strongly prefer >> to get rid of std::vector from the various interfaces, f.e. >> creating a >> constant array currently requires passing in an std::vector. For >> these sorts of interfaces, we

Hi folks, For the past month I’ve been working on improving the DominatorTree and PostDominatorTree in LLVM. The RFC that explains the motivations and plans can be found here: http://lists.llvm.org/pipermail/llvm-dev/2017-June/114045.html . Here’s a short summary of what changed upstream since posting it: - We switched from the Simple Lengauer-Tarjan algorithm for computing dominators

2009/4/1 Chris Lattner <clattner at apple.com>: > As far API design goes, we're in a mixed state.  I'd strongly prefer > to get rid of std::vector from the various interfaces, f.e. creating a > constant array currently requires passing in an std::vector.  For > these sorts of interfaces, we should migrate to passing in a "Constant > *const* / unsigned" pair.

...afe to use &V[0] > > when V is an empty std::vector > > Oh dear. That's a bit of a flaw in the plan. I suppose the solution is > to switch to SmallVector whenever this might be a problem. Or use iterators. That's why they're there. > For now I'm testing with ENABLE_EXPENSIVE_CHECKS=1, and it is indeed > catching lots of errors! Mm hmm. :) -Dave

...='' DATE='' DEBUG_RUNTIME='' DEFS='' DISABLE_ASSERTIONS='' DOT='' DOTTY='' DOXYGEN='' ECHO='echo' ECHO_C='' ECHO_N='-n' ECHO_T='' EGREP='' ENABLE_CBE_PRINTF_A='' ENABLE_DOXYGEN='' ENABLE_EXPENSIVE_CHECKS='' ENABLE_OPTIMIZED='' ENABLE_PIC='' ENABLE_THREADS='' ENABLE_VISIBILITY_INLINES_HIDDEN='' ENDIAN='' EXEEXT='' EXPENSIVE_CHECKS='' EXTRA_OPTIONS='' F77='' FFLAGS='' FIND='' FLEX='' GAS=''...

...with rtti enabled? Eventually I got it by editing every single Makefile in the "lib" sub-directories and commenting out the appropriate line "CXXFLAGS = -fno-rtti". However this can't be a proper solution. As stated earlier if REQUIRES_RTTI would be evaluated similiar to ENABLE_EXPENSIVE_CHECKS regarding rtti then it would be easy to enable rtti for clang. OTOH I'm not a makefile expert (to be honest I'm very far away from it). Thus maybe I'm just overlooking the right way to enable rtti for the clang libs. <--END--> Thanks in advance for any help... Best regards Ol...

...--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu; \ cd .. ; \ fi; \ (unset SDKROOT; \ make -C BuildTools \ BUILD_DIRS_ONLY=1 \ UNIVERSAL= \ ENABLE_OPTIMIZED=1 \ ENABLE_PROFILING= \ ENABLE_COVERAGE= \ DISABLE_ASSERTIONS=1 \ ENABLE_EXPENSIVE_CHECKS= \ CFLAGS= \ CXXFLAGS= \ ) || exit 1; checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking target system type... x86_64-pc-linux-gnu checking type of operating system we're going to host on... Linux checking type of operatin...

...39;' > DISABLE_ASSERTIONS='' > DOT='' > DOTTY='' > DOXYGEN='' > ECHO='echo' > ECHO_C='' > ECHO_N='-n' > ECHO_T='' > EGREP='' > ENABLE_CBE_PRINTF_A='' > ENABLE_DOXYGEN='' > ENABLE_EXPENSIVE_CHECKS='' > ENABLE_OPTIMIZED='' > ENABLE_PIC='' > ENABLE_THREADS='' > ENABLE_VISIBILITY_INLINES_HIDDEN='' > ENDIAN='' > EXEEXT='' > EXPENSIVE_CHECKS='' > EXTRA_OPTIONS='' > F77='' > FFLAGS='...