)]}'
{
  "commit": "13ef6eaba79be9f018ff1d978bd266cfa44d5fac",
  "tree": "ec6192fe8b09d09d99ea3f133b658d1fdffe3a43",
  "parents": [
    "b450abd17f4ab8d832a0d8beb1319804f2f5c6d6"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Wed Aug 28 18:47:56 2024 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu Aug 29 13:07:42 2024 +0000"
  },
  "message": "Extract C++ files, rather than C, when working around Bazel bugs\n\nTo work around Bazel\u0027s bugs around mixed C/C++ targets\n(https://github.com/bazelbuild/bazel/issues/22041), we automatically\nsplit all of our targets in two.\n\nWhen we did this, we originally pulled the C files into their own\ntarget. This had the side effect of building assembly files with the C\nfiles instead of with the C++ files. In principle, this does not matter,\nbut Bazel likes to turn targets into shared libraries, and our assembly\nfiles still contain a couple references to OPENSSL_ia32cap_P (see\nhttps://crbug.com/42290548). Those references rely on OPENSSL_ia32cap_P\nbeing a hidden symbol, and statically linked with the assembly files.\n\nPull the C++ out instead, to avoid this. Once\nhttps://crbug.com/42290548 is done, either will work, but this is\nneeded for now.\n\nBug: 362664827\nChange-Id: Icb929d194ee2311707fe1a0bb27ea0ccaf96a510\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70690\nReviewed-by: Bob Beck \u003cbbe@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8de6afb4e7a6c33158e0a0cb1c0550c1419d0052",
      "old_mode": 33188,
      "old_path": "util/util.bzl",
      "new_id": "83ddff6f95ac5ada7f04b1b351666bccdc586a08",
      "new_mode": 33188,
      "new_path": "util/util.bzl"
    }
  ]
}