Hi,
I can’t say if something like that is in preparation or even technically possible, but from my understanding such a signaling would not solve every topic, for example topics around priority-based task interruption, performance topics (nothing is faster then a flat memory access), and some other.
As I know, there’s exactly one case where a memory movement without transfer can lead to problems: accessing a variable by it’s address, that is not done cyclically. So making the needed ACCESS in CYCLIC instead of in INIT will prevent access violations caused by moved memory.
But maybe I’ve overseen something: what are your conrete use-cases, where memory movement without transfer leads to issues? And what programming language(s) do you use (I’m asking because of the usage of C/C++, where not only IEC variables are possible, but also “pure C variables”, which is maybe a different story)?
Best regards!