)]}'
{
  "commit": "8f2c220dc31ba2bf5c01a08272fb713632b8a5eb",
  "tree": "20af85a897691819e43b602f44d919f38f46d066",
  "parents": [
    "7f448d35a3d7ab4e7a39f84fe20c50f89b3031fb"
  ],
  "author": {
    "name": "Rudolf Polzer",
    "email": "rpolzer@google.com",
    "time": "Thu Nov 27 06:30:24 2025 -0800"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Mon Dec 08 09:13:01 2025 -0800"
  },
  "message": "Add a utility to extract identifiers from public headers.\n\nThis is experimental for now, and will later be used or changed to help\nwith symbol prefixing. The ultimate goal is finding a way to safely link\nBoringSSL and OpenSSL into the same binary, or even two BoringSSL\nversions; this tool is part of the effort of first analyzing the public\nsymbols BoringSSL is providing to figure out next steps.\n\nTested:\n  ```\n  for f in include/openssl/*.h; do echo \"#include \u003c${f#include/}\u003e\"; done |\\\n    clang++ -x c++ -std\u003dc++17 -Iinclude -fsyntax-only -Xclang -ast-dump\u003djson - \\\n    go run util/extract_identifiers_clang_json.go \u003e extract_identifiers.txt\n  ```\n  has identical output and no errors on both Linux and MacOS from\n  clang-16 to clang-next (which will become clang-22).\n\nBug: 42220000\nChange-Id: I3b3228242b29b8d97fa3a059e8e24caf91f39901\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/84708\nCommit-Queue: Adam Langley \u003cagl@google.com\u003e\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nAuto-Submit: Rudolf Polzer \u003crpolzer@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "37fc5d909d34506c9baa59c79f8c1773d089f91d",
      "new_mode": 33188,
      "new_path": "util/extract_identifiers_clang_json.go"
    }
  ]
}