(arising from email exchanges with Kiran Gullapalli, NXP - see emails around March 16, 2017)
Note: there is no timeline on these. Ie, as and when we can get to it.
disable VA for loop support (unless option --i-know-what-i-am-doing supplied)
augment VA syntax with a $solve_equations(...), which will call an NR (standalone NR supplied by VAPP and/or calling the simulator's NR). Useful for, eg, HISIM-HV.
Optimization modules:
HISIM-HV .m code has " (1==2 || 2==2 || 3==2...) " statements; can optimize them out
VA directives to not generate derivatives (useful for stuff inside the NR loop in HISIM-HV).
optimization module for detecting and re-using common sub-expressions. Compilers don't do it automatically.
code optimization to reduce instruction cache misses - can have significant performance impact (eg for PSP, HISIM, UTSOI2). Also target data cache.
"on demand code generation" - ie, model code specialized for given values of parameters (collapse out the expressions)
optimal set of branch voltage dependencies
adjust licensing so that others can write their own (proprietary) backends/adapters and keep them private. Eg, make an internal API for writing backends LGPL, while making the rest GPL?
(arising from email exchanges with Kiran Gullapalli, NXP - see emails around March 16, 2017) Note: there is no timeline on these. Ie, as and when we can get to it.