Target/Backend Plugin Extension

[ramang-unity]

Hi,

I was wondering if there is an extension system to add a new target into Slang without having to fork it? I currently tested by copying how the HLSL target is done. I had to change some core files. Is that the proper way to do it? It would be perfect if a target/backend could be a dynamically loadable module.

[mkeshavaNV]

Sorry, what kind of extension are you thinking about? What you have done seems to be like the right approach. Maybe send out a PR for review of what you already have?

[juliusikkala]

(I forgot to reply to this discussion earlier. I've recently added a target to Slang so this is still fresh in my mind)

Unfortunately, there currently is no such plugin system for adding new targets. It seems to me that it'd be difficult to create such a system, because different targets usually need different IR transformation passes (in slang-emit.cpp) and different mappings for builtins / intrinsics in core.meta.slang & hlsl.meta.slang. Trying to separate all of that to a dynamically loadable plugin would imply large architectural changes to the compiler. So your current approach makes sense.

There's also an upcoming GDC presentation that may be relevant to you: https://schedule.gdconf.com/session/were-speaking-your-slang-uage-here-a-proof-of-concept-console-backend-for-the-slang-shading-language-presented-by-nvidia/917503

[ramang-unity]

Thanks for the quick response.

It is good to know copying the HLSL target is the proper way to go. I will continue on with this method. Also thanks a lot for the GDC session info. That looks like a great session to attend.