1. 23 Aug, 2022 1 commit
  2. 22 Aug, 2022 1 commit
    • Support compilers that are unknown to CMake · c5615151
      Abseil failed to configure with `ABSL_PROPAGATE_CXX_STD` if the compiler was not known to CMake:
      
          target_compile_features no known features for CXX compiler
      
      Turns the error into a warning by checking `CMAKE_CXX_COMPILE_FEATURES`
      before calling `target_compile_features`.
      
      PiperOrigin-RevId: 469254470
      Change-Id: Ifba006dcdbf6a7112e382075b24678a792dbc827
      Abseil Team committed
  3. 18 Aug, 2022 2 commits
  4. 17 Aug, 2022 6 commits
  5. 16 Aug, 2022 3 commits
  6. 15 Aug, 2022 1 commit
  7. 12 Aug, 2022 3 commits
  8. 11 Aug, 2022 4 commits
  9. 10 Aug, 2022 3 commits
  10. 09 Aug, 2022 1 commit
  11. 05 Aug, 2022 3 commits
  12. 04 Aug, 2022 4 commits
    • debugging: handle alternate signal stacks better on RISCV · 9ab9e487
      In the case that we are unwinding with context, if the retreived frame pointer
      matches the signal context, assume that the value is valid and do not perform
      confidence checks.  In any other case, continue to perform some validation to
      avoid returning an incorrect frame pointer.
      
      Given that the VDSO path is currently untested, remove the code to simplify the
      logic in the frame walking.
      
      PiperOrigin-RevId: 465360612
      Change-Id: Iac656012182a12814bafecf20225ba68b90b4db1
      Saleem Abdulrasool committed
    • Revert change "Fix "unsafe narrowing" warnings in absl, 4/n.". · 4b551344
      The change breaks existing code by changing the return type of absl::bit_width.
      
      PiperOrigin-RevId: 465295951
      Change-Id: Id4ce7c2ac3699ce22aa2b4851a949f9e0104a3d7
      Thomas Köppe committed
    • Fix "unsafe narrowing" warnings in absl, 3/n. · 751ade00
      Addresses failures with the following, in some files:
      -Wshorten-64-to-32
      -Wimplicit-int-conversion
      -Wsign-compare
      -Wsign-conversion
      -Wtautological-unsigned-zero-compare
      
      (This specific CL focuses on .cc files in dirs n-t, except string.)
      
      Bug: chromium:1292951
      PiperOrigin-RevId: 465287204
      Change-Id: I0fe98ff78bf3c08d86992019eb626755f8b6803e
      Abseil Team committed
    • Fix "unsafe narrowing" warnings in absl, 4/n. · 07360899
      Addresses failures with the following, in some files:
      -Wshorten-64-to-32
      -Wimplicit-int-conversion
      -Wsign-compare
      -Wsign-conversion
      -Wtautological-unsigned-zero-compare
      
      (This specific CL focuses on .cc files in strings/, except /internal/.)
      
      Bug: chromium:1292951
      PiperOrigin-RevId: 465285043
      Change-Id: I37e9d1b4c4e9aa655b720da1467927af2aba995e
      Abseil Team committed
  13. 01 Aug, 2022 1 commit
    • Fix "unsafe narrowing" warnings in absl, 2/n. · 16af2bbc
      Addresses failures with the following, in some files:
      -Wshorten-64-to-32
      -Wimplicit-int-conversion
      -Wsign-compare
      -Wsign-conversion
      -Wtautological-unsigned-zero-compare
      
      (This specific CL focuses on .cc files in dirs a-h.)
      
      Bug: chromium:1292951
      PiperOrigin-RevId: 464541951
      Change-Id: If23b63ccea8e9b730159ff1c7288e9300a40b6bd
      Abseil Team committed
  14. 29 Jul, 2022 1 commit
    • debugging: honour `STRICT_UNWINDING` in RISCV path · dc370a82
      The changes in d6f96eda enabled handling cases
      where the stack may be non-contiguous or not fully symbolicated (e.g. in cases
      of alternate signal stacks).  However, it did not properly honour the requests
      from the caller to perform a strict unwinding where such frames are terminated
      upon the discontinuity.  This repairs that condition.
      
      Hoist the alignment check since that is safe to perform early.
      
      PiperOrigin-RevId: 464160529
      Change-Id: Ic65645928ec60c2a3b4844f3abd4fed1b991edab
      Saleem Abdulrasool committed
  15. 28 Jul, 2022 1 commit
    • Fix "unsafe narrowing" warnings in absl, 1/n. · 7f51ef5e
      Addresses failures with the following, in some files:
      -Wshorten-64-to-32
      -Wimplicit-int-conversion
      -Wsign-compare
      -Wsign-conversion
      -Wtautological-unsigned-zero-compare
      
      (This specific CL focuses on .h and win32 .inc files.)
      
      Bug: chromium:1292951
      PiperOrigin-RevId: 463835431
      Change-Id: If8e5f7f651d5cd96035e23e4623bdb08a7fedabe
      Abseil Team committed
  16. 27 Jul, 2022 2 commits
  17. 26 Jul, 2022 2 commits
    • Fix frame pointer alignment check. · b0787ae6
      The frame pointer sanity check in NextStackFrame() was more restrictive than it is necessary. The frame pointer is used to load the saved link-register and the address for the next stack frame. So it only needs to be 8-byte aligned. The aarch64 ABI does not specify an alignment requirement for the frame point.
      
      PiperOrigin-RevId: 463368519
      Change-Id: I473e05181603288f14734fe29013900c7505e201
      Abseil Team committed
    • Fixed sign-conversion warning in code. · 63c9eeca
      PiperOrigin-RevId: 463214218
      Change-Id: I54a37fd9560b480f9eaf0454670eacf875015fe8
      Abseil Team committed
  18. 25 Jul, 2022 1 commit