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 }}
Repository navigation
getting false negative error by SYCLomatic when migrating external CUDA host device function template #2192
error: explicit instantiation of 'foo' does not refer to a functiontemplate, variable template, member function, member class, or static data member
16 | extern template foo1<float>foo();
note: candidate template ignored: target attributes do not match
8 | __device__ __host__ foo1<Out>foo()
error: explicit instantiation of 'foo' does not refer to a functiontemplate, variable template, member function, member class, or static data member
17 | extern template foo1<double>foo();
note: candidate template ignored: target attributes do not match
8 | __device__ __host__ foo1<Out>foo()
changed the title [-]getting false negative error by SYCLomatic when migrating external CUDA function template[/-][+]getting false negative error by SYCLomatic when migrating external CUDA host device function template[/+]on Jul 23, 2024
I was wondering if this error hurt the later migration process even it is false negative? I tried to eliminate this error using user define rule to replace every extern template with empty line. However, the error still persist. it seems that user define rule is applied post migration? Can we decide when to apply the user define rule? (e.g. post migration vs pre migration)
@ArberSephirotheca, all user-defined rules are applied after the CUDA source code is parsed. Therefore, user-defined rules cannot eliminate the parsing error.
Activity
[-]getting false negative error by SYCLomatic when migrating external CUDA function template[/-][+]getting false negative error by SYCLomatic when migrating external CUDA host device function template[/+]tomflinda commentedon Jul 24, 2024
@ArberSephirotheca reproduced, thanks for your report, and we will plan to fix it.
ArberSephirotheca commentedon Jul 25, 2024
Thank you! @tomflinda
I was wondering if this error hurt the later migration process even it is false negative? I tried to eliminate this error using user define rule to replace every extern template with empty line. However, the error still persist. it seems that user define rule is applied post migration? Can we decide when to apply the user define rule? (e.g. post migration vs pre migration)
tomflinda commentedon Jul 26, 2024
@ArberSephirotheca, all user-defined rules are applied after the CUDA source code is parsed. Therefore, user-defined rules cannot eliminate the parsing error.