search for: esan

On Tue, Apr 19, 2016 at 11:19 PM, Sean Silva via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Some of this data might be interesting for profile guidance. Are there any > plans there? > > Esan instrumentation is geared toward application level tuning by developers -- the data collected here are not quite 'actionable' by the compiler directly. For instance, struct field reordering needs whole program analysis and can be very tricky to do for C++ code with complex inheritances (e.g...

Dear R users, I have a dataset with two variables: $esan - a grouping factor with 8 levels and $reus. I'd like to do wilcox.test on this dataset as sugested Weiwei here: https://stat.ethz.ch/pipermail/r-help/2007-July/136627.html. I tried to adapt his recommendation but no succes. Can anyone help me? Regards, Iurie Malai, Senior Lecturer Departmen...

Have you consider naming it `performance sanitizer` instead? I believe that it would be easier to misheard esan with asan, and psan would solve it. Besides, looks like fun! Good luck Piotr 17.04.2016 11:46 PM "Derek Bruening via llvm-dev" <llvm-dev at lists.llvm.org> napisał(a): TL;DR: We plan to build a suite of compiler-based dynamic instrumentation tools for analyzing targeted performanc...

TL;DR: We plan to build a suite of compiler-based dynamic instrumentation tools for analyzing targeted performance problems. These tools will all live under a new "EfficiencySanitizer" (or "esan") sanitizer umbrella, as they will share significant portions of their implementations. ==================== Motivation ==================== Our goal is to build a suite of dynamic instrumentation tools for analyzing particular performance problems that are difficult to evaluate using other...

...brought in > > but only read once. These could be candidates for non-temporal > > loads. > > > > > > ==================== > > EfficiencySanitizer > > ==================== > > > > > > We are proposing the name EfficiencySanitizer, or "esan" for short, > > to refer to this suite of dynamic instrumentation tools for > > improving program efficiency. As we have a number of different tools > > that share quite a bit of their implementation we plan to consider > > them sub-tools under the EfficiencySanitizer u...

...ing via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > TL;DR: We plan to build a suite of compiler-based dynamic instrumentation > > tools for analyzing targeted performance problems. These tools will all > > live under a new "EfficiencySanitizer" (or "esan") sanitizer umbrella, as > > they will share significant portions of their implementations. > > I will bike-shed the name as much as anyone else, but I'll stay away for > now :-) > > > > While these tools are not addressing correctness issues like other > &gt...

...ol will have inlined instrumentation to update shadow memory on either every memory access or in some cases just focusing on the heap; I do not have a number for code size expansion. The slowdown ranges were in the original email: 2x-5x. > We are proposing the name EfficiencySanitizer, or "esan" for short, to > refer > > to this suite of dynamic instrumentation tools for improving program > > efficiency. As we have a number of different tools that share quite a > bit > > of their implementation we plan to consider them sub-tools under the > > Efficiency...

...once. These could be candidates for non-temporal >> > loads. >> > >> > >> > ==================== >> > EfficiencySanitizer >> > ==================== >> > >> > >> > We are proposing the name EfficiencySanitizer, or "esan" for short, >> > to refer to this suite of dynamic instrumentation tools for >> > improving program efficiency. As we have a number of different tools >> > that share quite a bit of their implementation we plan to consider >> > them sub-tools under the Effic...

...y're > mutually exclusive either, i.e. both the profiling and XRay instrumentation > should be able to live together in the same binary). > Sanitizers (asan, tsan, ubsan, msan) are all program instrumenters. Asan also supports a mode for coverage testing. Profile related, we also have esan (efficiency sanitizer) under development. The sanitizer options of course are unified in its own category. David > So if it's just the two that will be interacting, then sharing flags > doesn't seem worth it. But if I'm missing another, then the case for > consolidating...

On Mon, Jun 27, 2016 at 2:53 PM Xinliang David Li <davidxl at google.com> wrote: > There is some misunderstanding about the intention of this flag. The > purpose of the flag is not to turn on profile instrumentation (which > already has -fprofile-instr-generate or -fprofile-generate for it), but to > select which instrumentors to use for PGO (IR or FE). I prefer fewer flags

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:

...N:BOOL=OFF //Generate dSYM files and strip executables and libraries (Darwin // Only) COMPILER_RT_EXTERNALIZE_DEBUGINFO:BOOL=OFF //Generate and build compiler-rt unit tests. COMPILER_RT_INCLUDE_TESTS:BOOL=ON //sanitizers to build if supported on the target (all;asan;dfsan;msan;tsan;safestack;cfi;esan;scudo) COMPILER_RT_SANITIZERS_TO_BUILD:STRING=asan;dfsan;msan;tsan;safestack;cfi;esan;scudo //Enable to build Debian packages CPACK_BINARY_DEB:BOOL=OFF //Enable to build IFW packages CPACK_BINARY_IFW:BOOL=OFF //Enable to build NSIS packages CPACK_BINARY_NSIS:BOOL=OFF //Enable to build RPM packa...