Skip to content
Snippets Groups Projects
  1. Nov 25, 2020
  2. Nov 21, 2020
  3. Aug 14, 2020
  4. May 15, 2020
  5. Apr 20, 2020
    • Stephan Hageboeck's avatar
      [CMake] Add build option "asan" for address sanitizer builds. · 6c19fdc8
      Stephan Hageboeck authored
      - Add build option `asan` to build with address sanitizer.
      - Add a suppression file etc/lsan-root.supp with leak sanitizer suppressions.
      - Add a directory core/sanitizer.
        - Add a micro library for configuring asan/lsan in ROOT. It is statically linked
          into all ROOT executables.
        - Create a target ROOT::ROOTStaticSanitizerConfig that exectuables can
          link against. This automatically pulls in the correct linker interface.
          This allows to create own sanitised executables that work with a
          sanitised ROOT.
        - Add a shared version of the config library for all cases where
          the address sanitizer run time is LD_PRELOADed into non-instrumented
          executables.
        - Add a README.md with more details.
      6c19fdc8
  6. Mar 26, 2020
  7. Feb 27, 2020
  8. Feb 17, 2020
  9. Jan 29, 2020
  10. Nov 14, 2019
  11. Sep 20, 2019
    • Axel Naumann's avatar
      [dictpch] From Wim: disable shell for subprocess.call: · d4365503
      Axel Naumann authored
      Wim says: adding 'shell=True' makes the command run on
      /bin/sh and allows you to use shell features (such as expansion and
      replacement of variables). But nothing in the command seems to need that
      feature, and anyway it's a risky thing to rely on, or what am I missing?
      
      Spawning an intermediate shell makes a mess of the environment when running
      under conda on Mac in the non-build environment. Running the normal way as
      per the patched line above, and all seems good.
      d4365503
  12. Sep 08, 2019
  13. Aug 23, 2019
  14. Aug 22, 2019
  15. Aug 12, 2019
    • Vassil Vassilev's avatar
      [pch] Reduce build system information exposed to the pch generation. · 10a0decf
      Vassil Vassilev authored
      The PCH configuration should match the runtime environment of ROOT so that
      whenever ROOT starts up, the PCH should match the precise invocation options
      of cling. In the past that was done by exporting plenty of build information
      from the build system to the pch generation (done via rootcling). However,
      this is not necessary anymore because rootcling and cling are much better
      fine tuned towards detecting the build environment and setting the runtime
      invocation options. Essentially, cling setup nowadays duplicates to some
      extent this logic deeming it needless. Verification of this claim is quite
      simple: ROOT will not start if the PCH build options mismatch.
      
      This patch simplifies the pch generation logic by relying more on the cling
      automatic detection of the build options.
      10a0decf
  16. Aug 06, 2019
  17. Jul 02, 2019
  18. May 11, 2019
    • Philippe Canal's avatar
      Suppress valgrind warning about fUniqueID unitialized memory used. · d5ecc717
      Philippe Canal authored
      This is done by taking the check of fUniqueID and the assignment to fBuits
      into a separate function and by including this function in the header
      *but* marking it as "noinline" to prevent its inlining and preserve a
      way to suppress the valgrind warning.
      
      Introducing the macro R__NEVER_INLINE which expands to
      
         inline __attribute__((noinline))
      
      The performance degradation is less than 10% for a case doing
      only creation and destruction of TObjects.
      d5ecc717
  19. Mar 07, 2019
  20. Mar 04, 2019
  21. Feb 28, 2019
  22. Feb 26, 2019
Loading