)]}'
{
  "commit": "2a412ea20590af081b534cbc55f868eb242bcb58",
  "tree": "ad708c18c0acfd8a13c685da6dd33ec6d4740277",
  "parents": [
    "3044c24181e96187c8c683208693bd9d2f2d4420"
  ],
  "author": {
    "name": "Chris Forbes",
    "email": "chrisforbes@google.com",
    "time": "Mon Sep 30 18:43:48 2019 -0700"
  },
  "committer": {
    "name": "Chris Forbes",
    "email": "chrisforbes@google.com",
    "time": "Tue Oct 01 14:41:04 2019 +0000"
  },
  "message": "Remove array restriction from EOpEqual, EOpNotEqual\n\nThe GLSL-version-specific behavior is already dealt with in earlier\nchecks; here we can assume we are dealing with GLSL ES 3.00.\n\nThe GLSL ES 3.00 spec section 5.7 explicitly calls out \u003d\u003d and !\u003d as\nbeing supported operations on arrays.\n\nThis is an unusual construct in real shaders, but it is used in the\nvarious \"complex expression\" tests (in an unreachable path).\n\nBug: b/141916742\nTest: dEQP-GLES3.functional.shaders.arrays.complex_expression.*\nChange-Id: I8a4ece122d604ffb917b94c03c8a086230e9108a\nReviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/36828\nTested-by: Chris Forbes \u003cchrisforbes@google.com\u003e\nKokoro-Presubmit: kokoro \u003cnoreply+kokoro@google.com\u003e\nReviewed-by: Nicolas Capens \u003cnicolascapens@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2c47256a65c9cc8ef83c8f5277c9867251230fce",
      "old_mode": 33188,
      "old_path": "src/OpenGL/compiler/Intermediate.cpp",
      "new_id": "c5fb3a2e45d8424cbb3bfc075b82e324afbff343",
      "new_mode": 33188,
      "new_path": "src/OpenGL/compiler/Intermediate.cpp"
    }
  ]
}