cuFFT LTO callback symbol name linkage

Hello,

I’ve had some problems running the new cuFFT LTO callbacks. What I found out is that the callback function cannot be defined as extern "C" otherwise an internal error is returned when creating the plan.

I don’t know if this is an expected behaviour or not, but I think it should be mentioned in the documentation. The reason I put the extern "C" before the function name was because I expected that either a C or C++ (mangled) name must be passed as the callbackSymbolName parameter and I did not want to deal with mangling.

Thank you.

Best regards
David

Hi @dejvbayer,

Thank you for the input, this feedback is very valuable to keep improving the feature.

One of our engineers will investigate and follow up to see if there is a possible work-around (beyond updating the docs).