)]}'
{
  "commit": "e026545ad5d91928b3cb9afde16e74fad612bfdb",
  "tree": "7fe66e338e118f9dfc2cc8684b22895c2c982f24",
  "parents": [
    "71aa720a990bed848628e0c3972574ea4ae075b6",
    "7ab025c8a18d3c3c7a93e914f4cabb9f055dd0cf"
  ],
  "author": {
    "name": "Ben Vanik",
    "email": "ben.vanik@gmail.com",
    "time": "Tue Jan 31 13:21:06 2023 -0800"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Tue Jan 31 13:21:06 2023 -0800"
  },
  "message": "Extending `iree_hal_allocator_t` with memory heaps and compat queries. (#12002)\n\nThe new `iree_hal_allocator_query_memory_heaps` API allows allocators to\r\nexpose the available memory heaps to external layers that need to make\r\ndecisions based on the characteristics of the underlying allocator.\r\n\r\nThe update to `iree_hal_allocator_query_buffer_compatibility` provides\r\npooling layers the ability to ask implementations to adjust the\r\nparameters and allocation size of a request without performing the\r\nallocation. A pooling layer that was trying to find an appropriate\r\nbucket or virtual addressing layer that needed to query for reservation\r\nranges can take the user params, have the implementation adjust them,\r\nand assume that any allocations made would have those exact parameters.\r\n\r\nTo aid flag/configuration utilities some bitfield parsing has been added\r\nfor HAL memory types that can be extended to all enums in the future.",
  "tree_diff": []
}