)]}'
{
  "commit": "94422c9447e52b9b383b75a88a71f5f6576f7bff",
  "tree": "c0669dbd33e791eae0d5748cb52edf07f80abc2f",
  "parents": [
    "07f8992b1ccae2ea6042acbe5f66ac434bc018f0"
  ],
  "author": {
    "name": "Cherry Zhang",
    "email": "cherryyz@google.com",
    "time": "Thu Jan 03 15:56:29 2019 -0500"
  },
  "committer": {
    "name": "Cherry Zhang",
    "email": "cherryyz@google.com",
    "time": "Thu Jan 10 16:03:26 2019 +0000"
  },
  "message": "passes: remove write barriers for stack writes\n\nStack writes don\u0027t need write barriers. Also it is bad if a write\nbarrier is applied to a write on an uninitialized slot.\n\nThe frontend already tries not to insert write barriers for stack\nwrites, but as it is based on AST, it may not identify all the\nstack writes. Here, with the SSA-based IR, we can identify the\nremaining stack writes and elide the write barriers.\n\nThis is not ideal: it doesn\u0027t remove the conditional branch that\ntests if the write barrier is enabled.\n\nChange-Id: I8d4b299bc2ab9af49e4b4302ca1252edad5a685d\nReviewed-on: https://go-review.googlesource.com/c/157138\nReviewed-by: Than McIntosh \u003cthanm@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ccd85019b35fec11844aa568fe4679a0db292a8e",
      "old_mode": 33188,
      "old_path": "passes/GoStatepoints.cpp",
      "new_id": "9fca55fc2459857d847bad93aea2518577a36fd6",
      "new_mode": 33188,
      "new_path": "passes/GoStatepoints.cpp"
    }
  ]
}