Skip to content

A
abseil-cpp
Switch branch/tag
  1. 23 Jun, 2022 1 commit
  3. 22 Jun, 2022 3 commits
    • Merge contiguous mappings from the same file. · 4dc63bad 
      This allows symbolization to work if different parts of a binary's text are mapped differently, e.g. if they're mlock()ed or mapped onto huge pages.

PiperOrigin-RevId: 456600880
Change-Id: I069264f94cf834df9201968275a00828f5eb077e
      Abseil Team committed
    • Update versions of WORKSPACE dependencies · e7cbb2ac 
      PiperOrigin-RevId: 456549823
Change-Id: Iee19597c63a653b8562168367d5860cf8421b6ae
      Derek Mauro committed
    • Use ABSL_INTERNAL_HAS_SSE2 instead of __SSE2__ · 8e27a618 
      This ensures that emmintrin.h is included with clang-cl. Otherwise, errors like
this occur:
.../absl/container/internal/raw_hash_set.h(536,8): error: unknown type name '__m128i'
inline __m128i _mm_cmpgt_epi8_fixed(__m128i a, __m128i b) {

This aligns the include ifdef guards and the guards that use the provided APIs.
The includes are also reordered, so they appear after the config header which
provides the internal macro values.

PiperOrigin-RevId: 456530271
Change-Id: I86dfd0022fd06fe7aa132138ec4d1bd14a86ba84
      Abseil Team committed
  5. 21 Jun, 2022 2 commits
  7. 17 Jun, 2022 1 commit
    • Update GoogleTest version used by Abseil · d2c5297a 
      As part of this update, GoogleTest is now using the Abseil flags
implementation, and the flags usage_test needs to be modified to pass.

If building with bazel and --define=absl=1 to force GoogleTest to use
Abseil, a WORKSPACE dependency on the abseil branch of the RE2 project
is now required.

PiperOrigin-RevId: 455512245
Change-Id: I2025df0c86006fac97a80713524c9d0aae8b358e
      Derek Mauro committed
  9. 16 Jun, 2022 5 commits
  11. 15 Jun, 2022 3 commits
  13. 14 Jun, 2022 6 commits
  15. 11 Jun, 2022 1 commit
  17. 10 Jun, 2022 3 commits
  19. 09 Jun, 2022 3 commits
  21. 08 Jun, 2022 2 commits
    • Add documentation on optional flags to the flags library overview. · e0a32c2a 
      PiperOrigin-RevId: 453766125
Change-Id: Id4d88ae20bdadc960a65bc1010eea746f1eba051
      Tom Manshreck committed
    • absl: correct the stack trace path on RISCV · 7a8d20b7 
      When we would perform a stacktrace using the frame pointer walking, because we
did the adjustment for the return address separately, we were misaligning the
stack size and frame.  Simplify the logic and correct the offset.

The recovered frame pointer provides us with the return address of the current
frame and the previous frame's frame pointer.  Subsequently, we decide if we
want to record this frame or not.  The value in `next_frame_pointer` already
points to the value from the previous stack frame (that is the next frame
pointer to iterate).  As such, the value computed by `ComputeStackFrameSize` is
the value for the current frame.  This was offset by one previously.

Take the opportunity to clean up some of the local comments, fixing typos and
splitting up the comments to reflect the lines that they are associated with.

PiperOrigin-RevId: 453744059
Change-Id: If14813e0ac36f327f4b7594472f2222d05c478aa
      Saleem Abdulrasool committed
  23. 07 Jun, 2022 2 commits
  25. 06 Jun, 2022 8 commits