)]}'
{
  "commit": "edfe4133d28c5e39d4fce6a2554f3e2b4cafc9bd",
  "tree": "d9a5d244759b142367617efeddfe5217fe44be33",
  "parents": [
    "565081680a6b432a5ddc275fcf2b11375a97f39c"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Mon Mar 22 16:28:22 2021 -0400"
  },
  "committer": {
    "name": "Adam Langley",
    "email": "agl@google.com",
    "time": "Tue Mar 23 17:32:33 2021 +0000"
  },
  "message": "Automatically enable C11 atomics when available.\n\nIt\u0027s now 2021. Hopefully we can at least assume anyone building with\n-std\u003dc11 also has a corresponding set of headers. Plus, even if you\ndon\u0027t, Clang seems to provide a header. (So C11 atomics work in\nclang-cl.) Also apparently atomics are optional, so this checks\n__STDC_NO_ATOMICS__.\n\nThis does *not* set C11 as the minimum version. If you build with\n-std\u003dc99, we\u0027ll silently use the non-atomics implementation. That\u0027s a\nlittle magical, so I\u0027ve kept OPENSSL_C11_ATOMIC as a way to assert that\nyou really want C11 atomics. Mostly it turns into a -std\u003dc11 \u0026\u0026 !MSVC\nself-assert.\n\nUpdate-Note: If something fails to compile, we\u0027ll revert this and adjust\nthe check, or add an opt-out, or give up. Also, if building with\n-std\u003dc99, consider -std\u003dc11.\n\nChange-Id: I1a8074c367a765c5a0f087db8c250e050df2dde8\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/46344\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c57464542137f139a586703b5272df832b63b759",
      "old_mode": 33188,
      "old_path": "crypto/internal.h",
      "new_id": "51d1d9cdba7b8966ed7b3168d7597a596d8a25ef",
      "new_mode": 33188,
      "new_path": "crypto/internal.h"
    }
  ]
}