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
The overall CUDA API migration support status is recorded in .csv files under <SYCLomatic/docs/dev_guide/api-mapping-status>and also in this online documentation: CUDA API Migration Support Status — . There are more than 50% of non-migrated APIs can be used by users' CUDA projects. A reporting tool to scan the project code base and list the statistics of non-migrated APIs can help evaluate the migration efforts.
A utility to answer the question - "How many unsupported CUDA APIs have been used in my project" can be useful in an early project study phase.
The overall CUDA API migration support status is recorded in .csv files under <SYCLomatic/docs/dev_guide/api-mapping-status>and also in this online documentation: CUDA API Migration Support Status — . There are more than 50% of non-migrated APIs can be used by users' CUDA projects. A reporting tool to scan the project code base and list the statistics of non-migrated APIs can help evaluate the migration efforts.
A utility to answer the question - "How many unsupported CUDA APIs have been used in my project" can be useful in an early project study phase.
The initial version - https://github.com/Joel-lin/sycl-mapping-api-scanner/blob/main/README.md
The text was updated successfully, but these errors were encountered: