AllocationsInfo allocates buffers for all module variables.

[nadavrot]

AllocationsInfo allocates buffers for all variables, and not only for variables that are used by the function. I think that this is okay for the JIT, but not so great for the AOT compilation because the unrelated variables become a part of the interface.

For more details see: AllocationsInfo::allocateWeightVars.

[opti-mix]

Other backends (e.g. OpenCL) have this issue as well and we'd better fix it there as well.

May be we should have a helper method or a filtering iterator that yields only variables used by a specific Function? Then we'd need to allocate buffers only for the variables returned by such a helper method or iterator.

[nickgg]

@opti-mix Is this still an issue?

[opti-mix]

Yes, I think it is not fixed yet.