Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
---|---|---|---|---|---|---|
configure.diff | Set package configuration options Configure Abseil for Debian. - Set the SONAME appropriately. - To minimize the possibility of future ABI breakage, treat absl::any, absl::optional, absl::string_view, and absl::variant as their own types (rather than aliases for the std:: versions), and compile everything in an inline namespace. - Enable upstream's hardened build mode. - Disable Intel SSE2 on i386, since Debian supports some i386 processors without that extension. Keep it enabled on amd64, since all amd64 processors have it. - Disable Intel SSSE3 entirely, since no i386 processor supports it and Debian supports amd64 processors without it. |
Benjamin Barenblat <bbaren@google.com> | not-needed | |||
fix-hppa.diff | Fix build on hppa | John David Anglin <dave.anglin@bell.net> | no | debian | ||
std-hash.diff | Work around broken std::hash on s390x On s390x, std::hash hashes large classes of data to the same value, which violates assumptions made by the Abseil tests. #ifdef out the test code that depends on those assumptions. |
Benjamin Barenblat <bbaren@google.com> | no | debian | ||
latomic.diff | Use libatomic if necessary 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. |
Benjamin Barenblat <bbaren@google.com> | no | debian | ||
cpu-frequency.diff | Ignore missing CPU frequency on more architectures Linux on MIPS, PA-RISC, RISC-V, and SystemZ doesn’t expose the nominal CPU frequency via /sys, so don’t worry if `NominalCPUFrequency` returns 1.0 on those platforms. Some POWER machines expose the CPU frequency; others do not. Since we can’t predict which type of machine the tests will run on, simply disable testing for `NominalCPUFrequency` on POWER. The author works at Google. Upstream applied this patch as Piper revision 347079873 and exported it to GitHub; the Applied-Upstream URL above points to the exported commit. |
Benjamin Barenblat <bbaren@google.com> | invalid | |||
nan-narrowing.diff | Avoid libgcc -NaN narrowing bug When testing -NaN parsing, avoid narrowing -NaN from double to float. This avoids a bug in libgcc (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98251). The author works at Google. Upstream applied this patch as Piper revision 347654751 and exported it to GitHub; the Applied-Upstream URL above points to the exported commit. |
Benjamin Barenblat <bbaren@google.com> | invalid | |||
endian-hash.diff | Remove endian-sensitivity from hash slow path Prior to this commit, the Abseil hash fast path was endian-agnostic, but the slow path assumed a little-endian platform. Change the slow path to be endian-correct, ensuring that values produced by the fast and slow paths are equal even on big-endian systems. The author works at Google. Upstream applied this patch as Piper revision 355424258 and exported it to GitHub; the Applied-Upstream URL above points to the exported commit. |
Benjamin Barenblat <bbaren@google.com> | invalid | |||
endian-random.diff | Remove endian-sensitivity from Abseil's RNG Ensure that the Abseil random number generator produces identical output on both big- and little-endian platforms by byte-swapping appropriately on big-endian systems. The author works at Google. Upstream applied this patch as Piper revision 355635051 and exported it to GitHub; the Applied-Upstream URL above points to the exported commit. |
Benjamin Barenblat <bbaren@google.com> | invalid | |||
ppc-float-conversion.diff | Fix float conversion for PPC. In PPC `long double` is a double-double representation which behaves weirdly wrt numeric_limits. Don't take `long double` into account when we are not handling `long double` natively anyway. Fix the convert test to always run the conversion even if we are not going to compare against libc's printf result. This allows exercising the code itself to make sure we don't trigger assertions or UB found by sanitizers. The author works at Google. Upstream applied this patch as Piper revision 355857729 and exported it to GitHub; the Applied-Upstream URL above points to the exported commit. |
Samuel Benzaquen <sbenza@google.com> | no | backport, https://github.com/abseil/abseil-cpp/commit/c36d825d9a5443f81d2656685ae021d6326da90c |