search for: llvm_enable_stat

Right now, the LLVM Statistic class does not increment values if we are in non-debug mode, unless you define LLVM_ENABLE_STATS (which, sadly, is also not available from cmake). Before i go and add it to cmake, i ran numbers. I can't find a single testcase, large or small, where enabling statistics all the time isn't completely noise. It looks like it was disabled in march 2013. https://reviews.llvm.org/D486 T...

...arSimplify. I understand NDEBUG as `remove >all the code only useful for developers`, independent of whether we >also want debug symbols. > >I'd find it more useful to discuss what should NOT be covered under >the blanket term LLVM_ENABLE_ASSERTIONS. Example from the past are >LLVM_ENABLE_STATS and LLVM_ENABLE_DUMP that once was also using >NDEBUG. +1 for bring up this topic. The code base sometimes uses #ifdef NDEBUG to guard the definitions of some struct/class members and functions. This means there are inherent ABI incompatibility between non-NDEBUG and NDEBUG object files. I...

...time option instead of a compile time one? > > > On Wed, May 31, 2017 at 7:39 AM, Daniel Berlin via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Right now, the LLVM Statistic class does not increment values if we are >> in non-debug mode, unless you define LLVM_ENABLE_STATS (which, sadly, is >> also not available from cmake). >> >> Before i go and add it to cmake, i ran numbers. >> >> I can't find a single testcase, large or small, where enabling statistics >> all the time isn't completely noise. >> >> It looks...

Hi all, During discussions about assertions in the Flang project, we noticed that there are a lot of cases in LLVM that #ifndef NDEBUG is used as a guard for non-assert code that we want enabled in debug builds. This works fine on its own, however it affects the behaviour of LLVM_ENABLE_ASSERTIONS; since NDEBUG controls whether assertions are enabled or not, a lot of debug code gets enabled in