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
{{ message }}
This repository was archived by the owner on Mar 21, 2024. It is now read-only.
This is because execute_on_stream doesn't combine with other execution policy properties. Unfortunately making it work that way would require an exponential explosion of intermediate policies:
The easiest solution is probably to just fold the functional of execute_on_stream into execute_with_dependencies, which can already express and hold streams.
The only downside with that approach is that .on().on().on() would leave you with a large tuple holding some useless streams.
thrust::device.on(stream).after(event)doesn't work; sort relies on doing.afterinternally, thusthrust::async::sort(thrust::device.on(stream), ...)doesn't work.This is because
execute_on_streamdoesn't combine with other execution policy properties. Unfortunately making it work that way would require an exponential explosion of intermediate policies:execute_with_allocator_and_streamexecute_with_dependencies_and_streamexecute_with_allocator_and_dependencies_and_streamThe easiest solution is probably to just fold the functional of
execute_on_streamintoexecute_with_dependencies, which can already express and hold streams.The only downside with that approach is that
.on().on().on()would leave you with a large tuple holding some useless streams.Also there is a testing gap here.