)]}'
{
  "commit": "ca85396d9990293c5456f7da5fc71cc5906eca0c",
  "tree": "1d514d86b6bca75237b56cb683b047654ff181f5",
  "parents": [
    "116db8778a4bbec72fedcdffccfa2c83ef7b4e1b"
  ],
  "author": {
    "name": "bjacob",
    "email": "benoitjacob@google.com",
    "time": "Thu Sep 22 15:50:40 2022 -0400"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Thu Sep 22 15:50:40 2022 -0400"
  },
  "message": "Make iree-benchmark-suites buildable with some backends disabled. (#10508)\n\nNote: the reason why iree-test-deps wasn\u0027t failing similarly was that\r\n`iree_single_backend_generated_trace_runner_test` and\r\n`iree_check_single_backend_test_suite` were already performing a similar\r\ncheck, but they do it on the `DRIVER`, not on the `TARGET_BACKEND`. They\r\ncan do so because these targets are built in the device build dir, where\r\n`IREE_HAL_DRIVER_*` variables are set and drivers are built, because\r\ndrivers are part of the runtime, so they\u0027re built in the device build\r\ndir.\r\n\r\nUnlike those targets, `iree-benchmark-suites` is built in the host build\r\ndir, so we shouldn\u0027t enable or disable benchmarks based on\r\n`IREE_HAL_DRIVER_*` here. Instead, what is relevant (and to the point of\r\nfixing the module compile error that caused me to look into this) is a\r\ncheck on `IREE_TARGET_BACKEND_*`.\r\n\r\nPossibly these could be unified by switching also `iree-test-deps` to\r\nthis `IREE_TARGET_BACKEND_*` check.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3795bd76c5f57d8edec5a99335226d08b5b131d1",
      "old_mode": 33188,
      "old_path": "build_tools/cmake/iree_benchmark_suite.cmake",
      "new_id": "9c38441040fecf8adab5ae0848dd705dca675136",
      "new_mode": 33188,
      "new_path": "build_tools/cmake/iree_benchmark_suite.cmake"
    }
  ]
}