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
Is your feature request related to a problem? Please describe
The kernel fusion integration into the scheduler was removed to make the scheduler leaner.
Some functions and classes could not be removed entirely, as doing so would constitute an ABI-breaking change. For the time being, they have been replaced with dummy implementations.
In the next ABI-breaking window, those stubs should then be removed entirely.
This includes:
Multiple entries in DataLessPropKind
queue::supports_fusion()
fusion_wrapper[.cpp/.hpp]
The supports_fusion device aspect
Describe the solution you would like
No response
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Remove the integration of kernel fusion from the SYCL runtime scheduler.
This makes the implementation of the scheduler less complex and leaner.
As a consequence, the experimental kernel fusion feature is no longer
supported, the extension proposal status has been updated.
Some stubs of the kernel fusion must remain for now to avoid ABI-break,
removing those stubs in the next ABI-breaking window is tracked through
#15184.
---------
Signed-off-by: Lukas Sommer <[email protected]>
Is your feature request related to a problem? Please describe
The kernel fusion integration into the scheduler was removed to make the scheduler leaner.
Some functions and classes could not be removed entirely, as doing so would constitute an ABI-breaking change. For the time being, they have been replaced with dummy implementations.
In the next ABI-breaking window, those stubs should then be removed entirely.
This includes:
DataLessPropKind
queue::supports_fusion()
fusion_wrapper[.cpp/.hpp]
supports_fusion
device aspectDescribe the solution you would like
No response
Describe alternatives you have considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: