1. 28 Nov, 2022 2 commits
  2. 23 Nov, 2022 2 commits
    • Fix AMD cpu detection. · e51b4ef7
      Currently we take generic/default code-path on AMD due to misspelling.
      Mostly helps with crc+memcpy:
      
      name                            old speed               new speed               delta
      BM_Memcpy/1                      156MB/s ± 1%            156MB/s ± 1%     ~           (p=0.563 n=18+18)
      BM_Memcpy/100                   6.38GB/s ± 1%           6.50GB/s ± 1%   +1.89%        (p=0.000 n=19+19)
      BM_Memcpy/10000                 14.6GB/s ± 1%           21.7GB/s ± 0%  +49.01%        (p=0.000 n=20+19)
      BM_Memcpy/500000                13.5GB/s ± 1%           19.9GB/s ± 0%  +47.35%        (p=0.000 n=18+17)
      
      PiperOrigin-RevId: 490572650
      Change-Id: Id7901321a23262c0ab62a2d82fae86cf42acf16d
      Ilya Tokar committed
    • CRC: Get CPU detection and hardware acceleration working on MSVC x86(_64) · c2e9ce1d
      Using /arch:AVX on MSVC now uses the accelerated implementation
      
      PiperOrigin-RevId: 490550573
      Change-Id: I924259845f38ee41d15f23f95ad085ad664642b5
      Derek Mauro committed
  3. 22 Nov, 2022 4 commits
  4. 21 Nov, 2022 2 commits
  5. 18 Nov, 2022 1 commit
  6. 17 Nov, 2022 1 commit
    • Release structured logging. · ebab79b5
      This stores the operands to LOG (and CHECK) as separate fields in a serialized protobuf.  The protobuf format is not yet published.
      
      PiperOrigin-RevId: 489275799
      Change-Id: I86d83671a6b1feb2bddd5bee51552907897ca8eb
      Andy Getzendanner committed
  7. 16 Nov, 2022 7 commits
  8. 15 Nov, 2022 4 commits
    • Add a new API for `extract_and_get_next()` in b-tree that returns both the… · 7c022b94
      Add a new API for `extract_and_get_next()` in b-tree that returns both the extracted node and an iterator to the next element in the container.
      
      Motivation: it can be useful, when calling `extract` to maintain an iterator next to the location of the extracted element. `std::set`, et al. allow for this because they have iterator stability. `absl::{flat,node}_hash_{set,map}` allow for this because they are guaranteed not to rehash when elements are removed so they also have iterator stability across calls to `extract()`. But b-tree doesn't support this use case without this API because removing elements can cause rebalancing, which invalidates iterators. We can get the next iterator without this API using `lower_bound(node_handle.value())`, but that requires an extra lookup.
      PiperOrigin-RevId: 488721247
      Change-Id: Id66f17311bf53678f536e4e4f070775f5ce0c542
      Evan Brown committed
    • Use AnyInvocable in internal thread_pool · 842560d2
      PiperOrigin-RevId: 488676817
      Change-Id: I13f15bb93ab6dda4c56caf969be3c14f84ada6a0
      Abseil Team committed
    • Remove absl/time/internal/zoneinfo.inc. It was used to guarantee · d6fa16c8
      availability of a few timezones for "time_test" and "time_benchmark",
      but (file-based) zoneinfo is now secured via existing Bazel data/env
      attributes, or new CMake environment settings.
      
      This also avoids the need for employing the CCTZ zone-info-source
      extension mechanism (which is a win).
      
      PiperOrigin-RevId: 488673952
      Change-Id: I9def9d705c8f0dca3c0bcddc2406edb098ea5da3
      Abseil Team committed
    • Updated documentation on use of %v · 3ed4ca1f
      Also updated documentation around FormatSink and PutPaddedString
      
      PiperOrigin-RevId: 488651398
      Change-Id: Ic6c586dbb8bea61df841a142f12d22c7e5b03f43
      Tom Manshreck committed
  9. 14 Nov, 2022 2 commits
  10. 11 Nov, 2022 2 commits
  11. 10 Nov, 2022 5 commits
  12. 09 Nov, 2022 3 commits
  13. 08 Nov, 2022 1 commit
  14. 07 Nov, 2022 3 commits
  15. 06 Nov, 2022 1 commit