Visible to Intel only — GUID: GUID-AE9D019A-528B-4187-9DDA-A6C0A4CDB262
DPCT1000
DPCT1001
DPCT1002
DPCT1003
DPCT1004
DPCT1005
DPCT1006
DPCT1007
DPCT1008
DPCT1009
DPCT1010
DPCT1011
DPCT1012
DPCT1013
DPCT1014
DPCT1015
DPCT1016
DPCT1017
DPCT1018
DPCT1019
DPCT1020
DPCT1021
DPCT1022
DPCT1023
DPCT1024
DPCT1025
DPCT1026
DPCT1027
DPCT1028
DPCT1029
DPCT1030
DPCT1031
DPCT1032
DPCT1033
DPCT1034
DPCT1035
DPCT1036
DPCT1037
DPCT1038
DPCT1039
DPCT1040
DPCT1041
DPCT1042
DPCT1043
DPCT1044
DPCT1045
DPCT1046
DPCT1047
DPCT1048
DPCT1049
DPCT1050
DPCT1051
DPCT1052
DPCT1053
DPCT1054
DPCT1055
DPCT1056
DPCT1057
DPCT1058
DPCT1059
DPCT1060
DPCT1061
DPCT1062
DPCT1063
DPCT1064
DPCT1065
DPCT1066
DPCT1067
DPCT1068
DPCT1069
DPCT1070
DPCT1071
DPCT1072
DPCT1073
DPCT1074
DPCT1075
DPCT1076
DPCT1077
DPCT1078
DPCT1079
DPCT1080
DPCT1081
DPCT1082
DPCT1083
DPCT1084
DPCT1085
DPCT1086
DPCT1087 [UPDATE]
DPCT1088
DPCT1089
DPCT1090
DPCT1091
DPCT1092
DPCT1093
DPCT1094
DPCT1095
DPCT1096
DPCT1097
DPCT1098
DPCT1099
DPCT1100
DPCT1101
DPCT1102
DPCT1103
DPCT1104
DPCT1105
DPCT1106
DPCT1107
DPCT1108
DPCT1109
DPCT1110
DPCT1111
DPCT1112
DPCT1113
DPCT1114
DPCT1115
DPCT1116
DPCT1117
DPCT1118
DPCT1119
DPCT1120
DPCT1121
DPCT1122
DPCT1123
DPCT1124
DPCT1125
DPCT1126
DPCT1127
DPCT1128
DPCT1129
DPCT1130
DPCT1131
DPCT1132
DPCT2001
DPCT3000
DPCT3001
DPCT3002
Visible to Intel only — GUID: GUID-AE9D019A-528B-4187-9DDA-A6C0A4CDB262
Analysis Mode
Analysis Mode generates a summary report that shows:
Lines of code that are migrated with confidence
Lines of code that are migrated imperfectly due to the language gap between CUDA* and SYCL*
An estimation of how much human effort will be required to complete the code migration
All migration issues are classified into one of three levels of manual effort:
Low Effort: Indicates an issue that the developer can solve in minutes.
Medium Effort: Indicates an issue that may take hours to solve.
High Effort: Indicates that there is not yet equivalent functionality provided in SYCL or SYCL ecosystem libraries for the CUDA API or the CUDA library API. In these cases, the developer will need to manually rewrite the functionality.
An example analysis report can be seen as follows:
reduction.cpp:
+ 26 lines of code (100%) will be automatically migrated.
- 22 APIs/Types - No manual effort.
- 4 APIs/Types - Low manual effort for checking and code fixing.
- 0 APIs/Types - Medium manual effort for code fixing.
+ 0 lines of code ( 0%) will not be automatically migrated.
- 0 APIs/Types - High manual effort for code fixing.
reduction_kernel.cu:
+ 77 lines of code ( 89%) will be automatically migrated.
- 7 APIs/Types - No manual effort.
- 63 APIs/Types - Low manual effort for checking and code fixing.
- 7 APIs/Types - Medium manual effort for code fixing.
+ 9 lines of code ( 10%) will not be automatically migrated.
- 9 APIs/Types - High manual effort for code fixing.
Total Project:
+103 lines of code ( 91%) will be automatically migrated.
- 29 APIs/Types - No manual effort.
- 67 APIs/Types - Low manual effort for checking and code fixing.
- 7 APIs/Types - Medium manual effort for code fixing.
+ 9 lines of code ( 8%) will not be automatically migrated.
- 9 APIs/Types - High manual effort for code fixing.Intel® DPC++ Compatibility Tool provides a command line option to enable this feature:
$ dpct --analysis-mode sample.cuIntel® DPC++ Compatibility Tool supports saving the report to a file:
$ dpct --analysis-mode --analysis-report-output-file=report.txt sample.cu