)]}'
{
  "commit": "1b52dcb350289b262a105471a75ef6c001beecae",
  "tree": "0ab9ad479a8e50f66b895aba6a9fd0c46111f9cb",
  "parents": [
    "bba13cb1ac190cb4b77f6e55b6875b84be34df01"
  ],
  "author": {
    "name": "Peter Collingbourne",
    "email": "pcc@google.com",
    "time": "Wed May 07 16:37:30 2025 -0700"
  },
  "committer": {
    "name": "Copybara-Service",
    "email": "copybara-worker@google.com",
    "time": "Wed May 07 16:38:36 2025 -0700"
  },
  "message": "Stop being strict about validating the \"clone\" part of mangled names\n\nSupport for parsing mangled symbol names with a \".something\" suffix\nin the demangler was originally added because the compiler was using\nthat for function cloning, but since then the compiler has started\nusing \".something\" suffixes in many other cases, such as function\nrenaming for ThinLTO and CFI. As a result, some symbols in binaries\nbuilt with these features would fail to demangle.\n\nSo instead of trying to validate what comes after the \".\" let\u0027s just\nstop parsing when we see a \".\", so that the symbols are demangled\ncorrectly. This behavior is consistent with libc++.\n\nPiperOrigin-RevId: 756054147\nChange-Id: I01e9e97eee32bee05ba243b615ed26a36b59591d\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "dc15b8e58499e0ab5e44185af41803e8abc89132",
      "old_mode": 33188,
      "old_path": "absl/debugging/internal/demangle.cc",
      "new_id": "5f62ebb89788b9cb3fe7c410fbccf0220389eddc",
      "new_mode": 33188,
      "new_path": "absl/debugging/internal/demangle.cc"
    },
    {
      "type": "modify",
      "old_id": "9c8225a7599ed7d2a5bb9ebf4539cc2af4e45a86",
      "old_mode": 33188,
      "old_path": "absl/debugging/internal/demangle_test.cc",
      "new_id": "2012184b21cef0e65876e77c71fa0f3268b2242c",
      "new_mode": 33188,
      "new_path": "absl/debugging/internal/demangle_test.cc"
    }
  ]
}