)]}'
{
  "commit": "cee89849ad5e88c1bc84177951950cbbb184f5d9",
  "tree": "247dea04a3f4f40d2042ce972e742a4325cbf4fb",
  "parents": [
    "0c8a01ade0e5349f5b0f9afd5e4de622599ae1da"
  ],
  "author": {
    "name": "Tom Hughes",
    "email": "tomhughes@chromium.org",
    "time": "Wed Oct 07 14:39:53 2026 -0700"
  },
  "committer": {
    "name": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu Oct 08 13:22:44 2026 -0700"
  },
  "message": "entropy: Avoid volatile post-increment under C++20\n\nC++20 deprecated pre- and post-increment on volatile lvalues, causing\nthe JITTER_APT FIPS break test path in MemoryAccessSampler::Next to fail\ncompilation with -Wdeprecated-volatile (Clang) and -Wvolatile (GCC) when\nbuilding BoringSSL consumers as C++20.\n\nUse compound assignment (which C++20 defect report P2327R1 un-deprecated\nwhen its result is discarded) to match the existing volatile memory\naccess in the same function.\n\nBug: b/333039464, b/491765858\nChange-Id: I2e233ce91c922441d744fb8ac084b9c35c4250e6\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/103828\nAuto-Submit: Tom Hughes \u003ctomhughes@chromium.org\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nPresubmit-BoringSSL-Verified: boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com \u003cboringssl-scoped@luci-project-accounts.iam.gserviceaccount.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f4767a8165816f903085d861b7890d1634d5f244",
      "old_mode": 33188,
      "old_path": "crypto/fipsmodule/entropy/jitter.cc.inc",
      "new_id": "8c751665fa31fcacc641a16f18dc984ad627dea3",
      "new_mode": 33188,
      "new_path": "crypto/fipsmodule/entropy/jitter.cc.inc"
    }
  ]
}