Skip to content
Snippets Groups Projects
  1. Oct 28, 2021
  2. Sep 09, 2021
  3. Sep 08, 2021
  4. Sep 07, 2021
  5. Sep 03, 2021
  6. Aug 30, 2021
  7. Aug 19, 2021
  8. Aug 16, 2021
    • scott snyder's avatar
      CxxUtils: Update stacktrace test for newer lcg versions. · 02d1ba81
      scott snyder authored
      With newer lcg versions, the system addr2line doesn't work because it's too old.
      Normally that doesn't matter, because we usually use eu-addr2line, which does
      work.  However, the stacktrace unit test forces the use of /usr/bin/addr2line
      (as the output formats are slightly different).
      
      Change stacktrace so that if we don't find /usr/bin/eu-addr2line we
      search PATH for addr2line, rather than hardcoding it.  Also adjust the
      unit test so that it should work with either addr2line or eu-addr2line.
      02d1ba81
  9. Jun 15, 2021
  10. Jun 11, 2021
  11. Jun 09, 2021
  12. Jun 08, 2021
  13. May 31, 2021
  14. May 12, 2021
  15. May 09, 2021
  16. May 04, 2021
  17. Apr 29, 2021
  18. Apr 28, 2021
  19. Apr 23, 2021
  20. Apr 11, 2021
  21. Apr 08, 2021
  22. Apr 02, 2021
  23. Mar 27, 2021
    • scott snyder's avatar
      CxxUtils: Make exctrace properly MT-safe. · 658bf04d
      scott snyder authored
      Update the exctrace collector to work properly in a MT environment.
      Change the static variables holding the trace to be thread_local.
      Further, retrieve the saved trace via calling a function, rather
      than accessing the variables directly.
      658bf04d
  24. Mar 20, 2021
    • scott snyder's avatar
      CxxUtils: c++20 fixes · 0c041e69
      scott snyder authored
      std:is_pod is deprecated in c++20.
      
      If a class is declared with a requires clause, the equivalent clause
      must be present for all function definitions outside of the class body.
      0c041e69
  25. Mar 11, 2021
  26. Feb 24, 2021
  27. Feb 19, 2021
  28. Feb 17, 2021
  29. Jan 11, 2021
    • Attila Krasznahorkay's avatar
      Taught CxxUtils about the SYCL_LANGUAGE_VERSION macro. · 00282999
      Attila Krasznahorkay authored
      The Intel compiler is no longer using the macro name CL_SYCL_LANGUAGE_VERSION,
      but rather SYCL_LANGUAGE_VERSION.
      
      At the same time still kept the CL_SYCL_LANGUAGE_VERSION check around as
      well, in case we would try to build the code with an older version of the
      Intel compiler.
      00282999
  30. Jan 08, 2021
    • Nils Krumnack's avatar
      fix all compiler warnings for AnalysisBase on latest MacOS · 602b780a
      Nils Krumnack authored
      New compiler, new set of warnings...
      
      The main theme here is that clang now checks for range-based for loops
      whether it introduces unneeded temporaries, i.e. if the user asks for
      a reference for the loop variable, but the iterator doesn't return a
      reference or a reference of a different type, or conversely if the
      user asked for `const auto`, but could have been `const auto&`.
      
      In practice that usually hits us as:
      ```
      for (const auto& jet : jetContainer)
      ```
      which should be:
      ```
      for (const auto *jet : jetContainer)
      ```
      
      Also a couple of places like this (which miss the `const` qualifier on
      the first template parameter):
      ```
      std::map<std::string,std::string> stringMap;
      for (const std::pair<std::string,std::string>& stringPair : stringMap)
      ```
      
      For the most part I just replaced the loop variable type with what
      seemed correct.  In a few places I put explicit comments as to why I
      chose the type.
      
      Also a fair number of warnings for unused member variables in various
      packages.  Since I am not an expert on any of these packages and this
      can point to an actual bug, I commented out all unused variables and
      added a comment for actual experts to check and remove.
      
      I removed a couple of checks for `this != nullptr` which were
      originally introduced to check whether the user called a member
      function via a null pointer.  However those checks are `assert`-based,
      so with cmake they won't be included when the user calls them from a
      release, making this check mostly useless.
      
      There some other warnings I fixed in the process that should hopefully
      be self-explanatory.
      602b780a
  31. Dec 21, 2020
  32. Dec 17, 2020
Loading