Skip to content

A
abseil-cpp
Switch branch/tag
  1. 09 Mar, 2023 3 commits
  3. 08 Mar, 2023 3 commits
    • Merge pull request #1395 from AtariDreams:const · d5d287dc 
      PiperOrigin-RevId: 515105001
Change-Id: I4a8ce8291ef3df23108dd21d8adb6752cde92dd0
      Copybara-Service committed
    • Introduce two new public APIs for parsing command line flags. · 297efcc9 
      ParseAbseilFlagsOnly
To be used to parse Abseil Flags only and classify the rest of the arguments.

ReportUnrecognizedFlags
To be used to report unrecognized flags.

PiperOrigin-RevId: 515082682
Change-Id: I73271b56cc512a5e78b5fcd035564b3672d62ca8
      Gennadiy Rozental committed
    • Synchronization: Add support for true relative timeouts using · b75a3ff4 
      monotonic clocks on Linux when the implementation uses futexes

After this change, when synchronization methods that wait are passed
an absl::Duration to limit the wait time, these methods will wait for
that interval, even if the system clock is changed (subject to any
limitations with how CLOCK_MONOTONIC keeps track of time). In other
words, an observer measuring the time with a stop watch will now see
the correct interval, even if the system clock is changed. Previously,
the duration was added to the current time, and methods would wait
until that time was reached on the possibly changed realtime system
clock.

The behavior of the synchronization methods that take an absl::Time is
unchanged.  These methods always wait until the absolute point in time
is reached and respect changes to the system clock. In other words, an
observer will always see the timeout occur when a wall clock reaches
that time, even if the clock is manipulated externally.

Note: ABSL_PREDICT_FALSE was removed from the error case in Futex as
timeouts are handled by this case, and timeouts are part of normal
operation.
PiperOrigin-RevId: 515043788
Change-Id: I151127b588065bd1316273f36d7c946545c2c892
      Derek Mauro committed
  5. 07 Mar, 2023 2 commits
  7. 06 Mar, 2023 1 commit
  9. 03 Mar, 2023 1 commit
  11. 02 Mar, 2023 5 commits
  13. 28 Feb, 2023 2 commits
  15. 27 Feb, 2023 3 commits
  17. 26 Feb, 2023 1 commit
  19. 24 Feb, 2023 2 commits
    • Remove extra space in comment. · f2b52372 
      PiperOrigin-RevId: 512155216
Change-Id: Ie66d29bd48ba8523f5fb7f835f721d9aec637eba
      Abseil Team committed
    • Update the predicate for `ABSL_INTERNAL_HAS_RTTI` for Windows builds. · 8c79530e 
      Abseil defines `ABSL_INTERNAL_HAS_RTTI` by:

```
!defined(__GNUC__) || defined(__GXX_RTTI)
```

This predicate correctly decides rtti for GNU platforms. This predicate is always true for non-GNU platforms.

It is not true that rtti is always enabled for non-GNU platforms. For example, when building with `cl.exe` and disabling rtti with `\GR-`, this clause is true. This leads to errors in Windows builds that disable rtti.

This default behavior is not decidably correct, but the default behavior shouldn't change. It is better to guess that rtti is on, because if rtti is actually off, compilation will fail, and no programs will be harmed.

This change updates the non-default behavior to include a check for rtti on Windows platforms. This change preserves the default behavior.

PiperOrigin-RevId: 512085922
Change-Id: I1add0b9b8ca2de5d1313c8aed5ba2019632ab68a
      Abseil Team committed
  21. 23 Feb, 2023 6 commits
  23. 22 Feb, 2023 4 commits
  25. 21 Feb, 2023 6 commits
  27. 18 Feb, 2023 1 commit
    • fix(CMake): correct target variable for DLLs · bd624d9f 
      The `_dll` variable contains the target name. The code
was trying to use `_NAME` when handling ABSL_PROPAGATE_CXX_STD.
Probably a cut&paste error from the other places where we
handle that option.

PiperOrigin-RevId: 510551097
Change-Id: I006435978333dd7a72a300503389a7bf48fb6d0d
      Abseil Team committed