Skip to content

A
abseil-cpp
Switch branch/tag
  1. 09 Jan, 2023 2 commits
  3. 07 Jan, 2023 2 commits
  5. 06 Jan, 2023 2 commits
  7. 05 Jan, 2023 2 commits
  9. 04 Jan, 2023 3 commits
  11. 03 Jan, 2023 1 commit
  13. 29 Dec, 2022 1 commit
    • direct_mmap: Use off_t on linux · 45fdade6 
      off64_t is not provided without defining _LARGEFILE64_SOURCE on musl
this define is not defined automatically like glibc where it gets
defined when _GNU_SOURCE is defined. Using off_t makes it portable
across musl/glibc and for using 64bit off_t on glibc 32bit systems
-D_FILE_OFFSET_BITS=64 can be defined during build via CXXFLAGS

Signed-off-by: Khem Raj <raj.khem@gmail.com>
      Khem Raj committed
  15. 28 Dec, 2022 3 commits
  17. 27 Dec, 2022 1 commit
  19. 22 Dec, 2022 6 commits
  21. 21 Dec, 2022 3 commits
  23. 20 Dec, 2022 2 commits
  25. 19 Dec, 2022 5 commits
  27. 17 Dec, 2022 1 commit
  29. 16 Dec, 2022 2 commits
  31. 15 Dec, 2022 2 commits
    • Fix the documentation of the atomic_hook.h registration functions to correctly… · d241d919 
      Fix the documentation of the atomic_hook.h registration functions to correctly state that only the first registered hook will be honored.

The comments that imply otherwise were never true, and were a leftover artifact during initial development of the feature.

Also remove a TODO() I gave myself years ago; this is never going to happen and isn't worth the bother.

PiperOrigin-RevId: 495687371
Change-Id: I63f8ef57d659075bf290caae0617ea61ceb2c1db
      Greg Falcon committed
    • Add the ability to turn on warnings that get disabled in tests · e2416566 
      in GCC and LLVM build configs

This was accomplished by adding GccStyleFilterAndCombine() in copts.py

Previously, if we had a default warning of the form -Wwarning, adding
-Wno-warning to the list of test warnings would just add conflicting
flags. We now filter -Wwarning if -Wno-warning is added to the test warnings.

PiperOrigin-RevId: 495683815
Change-Id: I5dfd8a30b0be09d6b48237f61d598230ab9027db
      Derek Mauro committed
  33. 14 Dec, 2022 1 commit
  35. 13 Dec, 2022 1 commit
    • Prevent all CHECK functions from expanding macros for the error string. · a13ef44b 
      This was likely an unintentional behavior change made a while ago while trying to reduce duplication.  The new behavior will always include the unexpanded macro in the error string.  For example, `CHECK_EQ(MACRO(x), MACRO(y))` will now output "MACRO(x) == MACRO(y)" if it fails.  Before this change, CHECK and QCHECK were the only macros that had this behavior.

Not using function-like macro aliases is a possible alternative here, but unfortunately that would flood the macro namespace downstream with CHECK* and break existing code.

PiperOrigin-RevId: 495138582
Change-Id: I6a1afd89a6b9334003362e5d3e55da68f86eec98
      Mike Kruskal committed