Pre-requisites for Memory optimizations by analysing Solidity code

[NunoFilipeSantos]

What

Following the template of #13378, we want to do more complex analysis on the Solidity level, resulting in annotations of the AST that can be used during code generation to produce more optimal code, resp. code that can be handled better by the optimiser.

In particular, we want to address low-hanging fruit in memory optimizations, i.e. for any memory allocation in Solidity that we can easily determine to be temporary, we do not permanently allocate memory.

Tasks

• AST Property tests #14309
• unchecked increment for simple counter for loops #13378

Related Previous Issues

• Lifetime tracking for temporary memory objects #12351
• [Yul Optimizer] Consider moving statically sized memory allocations to static offsets while adjusting the memoryguard #13046 [by determining non-recursive static allocations in Solidity analysis and assigning those fixed offsets before codegen]

Similar Issues to be solved with a similar mechanism, but merely optionally to be done as part of this epic:

• Eliminate array bounds check for trivial case #13288