CMake/AbseilHelpers.cmake | 3 2 + 1 - 0 !
absl/base/options.h | 12 6 + 6 - 0 !
2 files changed, 8 insertions(+), 7 deletions(-)

 set package configuration options

absl/base/config.h | 8 3 + 5 - 0 !
1 file changed, 3 insertions(+), 5 deletions(-)

 canonicalize supported cpu feature set

absl/copts/AbseilConfigureCopts.cmake | 4 4 + 0 - 0 !
1 file changed, 4 insertions(+)

 use libatomic if necessary
Bug-Debian: https://bugs.debian.org/973492

On some architectures, notably armel, Abseil needs symbols defined in
libatomic. Abseil does not currently have a well-developed system to
declare external library dependencies, so just have the linker determine
if anything needs libatomic and add the DT_NEEDED entry where necessary.

absl/flags/CMakeLists.txt | 2 0 + 2 - 0 !
1 file changed, 2 deletions(-)

 eliminate libabsl_flags.so and libabsl_flags.a

CMake/AbseilHelpers.cmake | 2 2 + 0 - 0 !
1 file changed, 2 insertions(+)

 do not leak -maes -msse4.1 into pkgconfig

absl/strings/internal/cordz_info_statistics_test.cc | 2 2 + 0 - 0 !
1 file changed, 2 insertions(+)

---

absl/container/internal/raw_hash_set.cc | 5 5 + 0 - 0 !
absl/container/internal/raw_hash_set.h | 33 32 + 1 - 0 !
absl/container/internal/raw_hash_set_test.cc | 8 8 + 0 - 0 !
3 files changed, 45 insertions(+), 1 deletion(-)

 [patch] fix potential integer overflow in hash container
 create/resize

The sized constructors, reserve(), and rehash() methods of
absl::{flat,node}_hash_{set,map} did not impose an upper bound on
their size argument. As a result, it was possible for a caller to pass
a very large size that would cause an integer overflow when computing
the size of the container's backing store. Subsequent accesses to the
container might then access out-of-bounds memory.

The fix is in two parts:

1) Update max_size() to return the maximum number of items that can be
stored in the container

2) Validate the size arguments to the constructors, reserve(), and
rehash() methods, and abort the program when the argument is invalid

We've looked at uses of these containers in Google codebases like