Problem with FuseOps (and embedded constants in TIR)

Hi @kparzysz ,

Sorry to hear that there was downstream failure because of #8509.

I am also wondering how this is true, because of the following (note that we just used what was supported in TVM via LinkedParam node) :

The above are called respectively in the following locations :

We need to fix this if it is not happenning. @kparzysz would you be able to file an issue ? attn : @dmitriy-arm @Mousius

I think we need to move the link-params to be a property of the TIR backend (i.e. target).

However, the above seems to be the workaround of the issue, the real issue I suspect is hexagon backend expect LinkedParams node if --link-params is used, however, there is not a unit test (a simple codegen one) to assert this – that should have been broken by #8509.