)]}'
{
  "commit": "f3f8dfd8dd6e42a7f98b3b3c7a55516abd316c91",
  "tree": "18f39e91e2d183c659c682fd78e78231935a1bc3",
  "parents": [
    "21621d9ac9fb0ee441b88767737891a89e70c96d"
  ],
  "author": {
    "name": "Bruce Dawson",
    "email": "brucedawson@chromium.org",
    "time": "Tue Oct 13 11:14:36 2015 -0700"
  },
  "committer": {
    "name": "Paul Wankadia",
    "email": "junyer@google.com",
    "time": "Wed Oct 14 22:23:32 2015 +0000"
  },
  "message": "Use intrinsic for write barrier when applicable\n\nx86 and x64 CPUs have a strong memory model where writes never pass\nwrites, and reads never pass reads. The memory model is strong enough\nthat it is automatically consistent with write-release and read-acquire\nmemory barriers. Therefore, all that is needed for WriteMemoryBarrier()\nis an intrinsic to tell the compiler not to move code past the\nbarrier.\n\nThis change detects x86 and x64 CPUs on Windows and uses the\n_WriteBarrier() intrinsic\n\nChange-Id: I62263c0efb94cf1399b69f8de0dc225ae0a1325d\nReviewed-on: https://code-review.googlesource.com/3590\nReviewed-by: Paul Wankadia \u003cjunyer@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "695425c268ecff737ea55cef66ba816c46255841",
      "old_mode": 33188,
      "old_path": "util/atomicops.h",
      "new_id": "6007b560df3b6b13e9e0bfa39780c86d8d351a65",
      "new_mode": 33188,
      "new_path": "util/atomicops.h"
    }
  ]
}