1. 15 Aug, 2023 3 commits
  2. 14 Aug, 2023 3 commits
  3. 11 Aug, 2023 2 commits
  4. 10 Aug, 2023 4 commits
  5. 09 Aug, 2023 2 commits
  6. 08 Aug, 2023 7 commits
  7. 07 Aug, 2023 2 commits
  8. 04 Aug, 2023 4 commits
    • Release the `DFATAL` pseudo-LogSeverity level · 70172ada
      `DFATAL` is defined as `FATAL` in debug mode, and as `ERROR`
      when `NDEBUG` is defined.
      
      Closes #1279
      
      PiperOrigin-RevId: 553904244
      Change-Id: Iaa207ee65b2a39b4b7f5da241208c3d39cd5da0e
      Derek Mauro committed
    • Import of CCTZ from GitHub. · 659b77b7
      PiperOrigin-RevId: 553878129
      Change-Id: I054a5bd4c9011155c9fe03df0f07803ad7d2ade3
      Abseil Team committed
    • Store infoz on the heap instead of inline and store it only when we are sampling… · 8f241e77
      Store infoz on the heap instead of inline and store it only when we are sampling the current allocation.
      
      PiperOrigin-RevId: 553847957
      Change-Id: Idd131d0362bf36bd22d9bd20df54bd9ae50f0e28
      Evan Brown committed
    • Optimize Swissmap Match on Arm. · 039d70f6
      Currently we require only a single bit to be set in each abstract bit for iterable bitmasks. However, in most cases, where we have a single match, or no matches in a group, iteration is not needed. We move the masking to the iteration function instead of having it as a requirement for iterable Bitmask construction.
      
      This is 4-8% faster for Find and Insert operations.
      
      This can hurt performance if we need to iterate many times (there are many matches in the same Group), however this is unlikely, even if we assume the table is completely full.
      
      If there are 0 or 1 matches in a group, or the first match is the correct item we are looking for, we save 1 instruction/cycle (most cases)
      If there are 2 matches in a group, and the first is a false positive, this is neutral (< 3%)
      If there are more than 2 matches in a group and the first two are false positives, this can be slower by 1 cycle/instruction per additional iteration (< 0.1%)
      
      No change to x86.
      
      PiperOrigin-RevId: 553831814
      Change-Id: I08620899847eaf0086da989d829a1029ea24173a
      Connal de Souza committed
  9. 03 Aug, 2023 1 commit
  10. 02 Aug, 2023 3 commits
  11. 01 Aug, 2023 8 commits
  12. 31 Jul, 2023 1 commit
    • PR #1498: Fix order of link options in pkg-config files · 407f2fdd
      Imported from GitHub PR https://github.com/abseil/abseil-cpp/pull/1498
      
      In Windows, a few libraries (`dbghelp`, `advapi32`, and `bcrypt`) are added via link options. However, the .pc files produced for pkg-config erroneously include them before the abseil libraries. This can cause undefined references when trying to build against abseil.
      
      This commit swaps the order and adds the custom link options after the abseil dependencies. The following is a list of `.pc` files affected by this and the additional link options used:
      
      * all: `-L${libdir}`
      *  `absl_base.pc`: `-ladvapi32`
      * `absl_random_internal_seed_material.pc`: `-lbcrypt`
      * `absl_symbolize.pc`: `-ldbghelp`
      
      Closes https://github.com/abseil/abseil-cpp/issues/1497
      
      Merge af61f6d5d5fa7b390fc2e009652cd6da68b0fd38 into c9c0fd51
      
      Merging this change closes #1498
      
      COPYBARA_INTEGRATE_REVIEW=https://github.com/abseil/abseil-cpp/pull/1498 from stanhu:sh-fix-pc-link-order af61f6d5d5fa7b390fc2e009652cd6da68b0fd38
      PiperOrigin-RevId: 552564626
      Change-Id: I9d2a6ab99993bb4315dc94eade2cd419f1109c13
      Stan Hu committed