- Software
- IQANdesign
-
Ideas
Memory utilization when instantiating multiple identical external library function groups
When IQANdesign does not provide a native function/operation, such a function/operation could be implemented in an external library, for repeated use in application logic.
Currently, the benefit of implementing the function in an external library is that any future change of said function/operation would only have to be done once, which is great.
But, would it not be possible to also save memory? I.e. could it be possible that multiple instances of the same external library function group would only be instantiated once in application memory, even though it is called multiple times per cycle?
(Unrelated to the topic, but related to the origin of the topic, do you have any plans to introduce native functions for most- and least significant bit indexing? E.g. using de Bruijn multiplication/lookup tables would be so much cheaper if done natively.)
Thanks!
Customer support service by UserEcho
Instances of channels will be needed.
With the concept in IQAN where every channel holds a value that is accessed by channel, and where the control flow follows a strict calculation order, I do not see any way of incorporating that type of classic function call approach.
I do not have enough understanding of the underlying interpreter to comment further. I will just add that, I suppose my idea was that only the result(s) from each call to the same function in the same cycle would be memorized (as opposed to all computations within), though I suppose this would impair the online debug/measure view. If this is not possible or feasible you may close this topic.