)]}'
{
  "commit": "b121b74639b9d1a7dc3cdfd25ecd27efa4ac400c",
  "tree": "efc80800df31ab57178bcd11adb0908a616a739c",
  "parents": [
    "20572b4ec7e4e68ac15c56227351c7db17cc1d32"
  ],
  "author": {
    "name": "Nicolas Capens",
    "email": "capn@google.com",
    "time": "Thu Aug 01 13:22:34 2019 -0400"
  },
  "committer": {
    "name": "Nicolas Capens",
    "email": "nicolascapens@google.com",
    "time": "Sat Aug 10 08:16:32 2019 +0000"
  },
  "message": "Implement writing B10G11R11 in the Blitter\n\nThis does not yet handle rounding correctly, nor are Inf and NaN\ninput values dealt with.\n\nNote that the Vulkan 1.1.117 spec refers to\nhttps://www.khronos.org/registry/DataFormat/specs/1.2/dataformat.1.2.html#11bitfp\nfor the specification on the interpretation of 11- and 10-bit floating-\npoint formats, while that spec itself states that:\n\"Note that in general conversion from a real number to any\nrepresentation may require rounding, truncation and special value\nmanagement rules which are beyond the scope of a data format\nspecification and may be documented in APIs which generate these\nformats.\"\n\nThe Vulkan spec however does not document any specific conversion\nrequirement (in contrast, it does for the shared exponent format).\n\nBug: b/138944025\nChange-Id: If59adfb02f2793f69a028d379a03c05f9a12bd89\nReviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/34828\nPresubmit-Ready: Nicolas Capens \u003cnicolascapens@google.com\u003e\nTested-by: Nicolas Capens \u003cnicolascapens@google.com\u003e\nKokoro-Presubmit: kokoro \u003cnoreply+kokoro@google.com\u003e\nReviewed-by: Ben Clayton \u003cbclayton@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b4ca5f31f3bc000fcb1bf782a27a4d7ad304883c",
      "old_mode": 33188,
      "old_path": "src/Device/Blitter.cpp",
      "new_id": "06425db776dad1cf93971e11c2f2e44e6e6fc3ad",
      "new_mode": 33188,
      "new_path": "src/Device/Blitter.cpp"
    }
  ]
}