You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One possible outcome is we simply keep things as they are, but there may be a better option. In particular, if "device" CPU compilation/execution could be offloaded in a similar way as for GPU devices, there would be a better alignment between the SPIR-V CPU Runner and e.g. the Vulkan Runner.
The text was updated successfully, but these errors were encountered:
See this discussion for more details: https://github.com//pull/114563#discussion_r1831742718
One possible outcome is we simply keep things as they are, but there may be a better option. In particular, if "device" CPU compilation/execution could be offloaded in a similar way as for GPU devices, there would be a better alignment between the SPIR-V CPU Runner and e.g. the Vulkan Runner.
See this discussion for more details: #114563 (comment)
One possible outcome is we simply keep things as they are, but there may be a better option. In particular, if "device" CPU compilation/execution could be offloaded in a similar way as for GPU devices, there would be a better alignment between the SPIR-V CPU Runner and e.g. the Vulkan Runner.
The text was updated successfully, but these errors were encountered: