Visible to Intel only — GUID: GUID-5121A45E-1A44-4C49-9455-3F984617443A
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
Message
Detailed Help
Suggestions to Fix
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
DPCT1088
DPCT1089
DPCT1090
DPCT1091
DPCT1092
DPCT1093
DPCT1094
DPCT1095
DPCT1096
DPCT1097
DPCT1098
DPCT1099
DPCT1100
Visible to Intel only — GUID: GUID-5121A45E-1A44-4C49-9455-3F984617443A
DPCT1034
Message
The migrated API does not return an error code. 0 is returned in the lambda. You may need to rewrite this code.
Detailed Help
Typically, this happens because the API call in the original application returns an error code and then it is consumed by the program logic.
SYCL* uses exceptions to report errors and does not return the error code.
The Intel® DPC++ Compatibility Tool inserts a return 0; statement at the end of the lambda expression, if the return code is expected by the program logic and the new API does not return it. Review all such places in the code.
Similar to DPCT1003.
Suggestions to Fix
If in a DPC++ application you:
Do not need the code that consumes the error code, remove the code and the return 0; statement.
Need the code that consumes the error code, try to replace it with an exception handling code and use your logic in an exception handler.
Similar to DPCT1003.