)]}'
{
  "commit": "de12e3cabcb466cdf96c90d9bff0d919af71d561",
  "tree": "5de0b124ef9a5de9be17077cb9bc4e3c41a861a1",
  "parents": [
    "3950d6ce25c263c3d131985edfcd6b0899a7949e"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Tue Feb 14 10:36:29 2023 -0500"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Feb 14 19:19:32 2023 +0000"
  },
  "message": "Unify the two copies of bn_add_words and bn_sub_words\n\nCompilers are fine at inlining functions nowadays. We can hide the\nBN_ULLONG vs. manual carry extraction inside an inline function. I\u0027ve\npatterned the type signatures intentionally after Clang\u0027s builtins, in\ncase we want to use them in the future.\n\n(Previously I wrote in\nhttps://boringssl-review.googlesource.com/c/boringssl/+/56966 that the\nbuiltins weren\u0027t good on aarch64. This wasn\u0027t quite right. Rather, they\nwere bad on both x86_64 and aarch64 in LLVM 13, but they\u0027re fine on both\nin LLVM 14. My machine\u0027s Xcode was just a little old.)\n\nChange-Id: I666466dce7a146d5e49e94ff372ea018b610ef34\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/57245\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: Bob Beck \u003cbbe@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bf4971f1604883cf252d06717e0fac1b091b1163",
      "old_mode": 33188,
      "old_path": "crypto/fipsmodule/bn/generic.c",
      "new_id": "e4f4518e94949d991735d0658b4e33772fc8ff49",
      "new_mode": 33188,
      "new_path": "crypto/fipsmodule/bn/generic.c"
    }
  ]
}