Split expressions into atomic expressions. In other words, introduce
as many new local variables as necessary so that an expression is made at most of one operator. The rational for that is to obtain a lic code that is trivial to clock check (nested node calls, for example, make it less simple). The old behavior can still be obtained using --keep-nested-calls. During that change, I realised that I did not clock check asserts. Hence, I have also added this check.
Showing
- src/Makefile 2 additions, 0 deletionssrc/Makefile
- src/TODO 4 additions, 8 deletionssrc/TODO
- src/compiledData.ml 2 additions, 2 deletionssrc/compiledData.ml
- src/evalClock.ml 70 additions, 20 deletionssrc/evalClock.ml
- src/evalClock.mli 11 additions, 5 deletionssrc/evalClock.mli
- src/evalType.ml 33 additions, 12 deletionssrc/evalType.ml
- src/evalType.mli 10 additions, 3 deletionssrc/evalType.mli
- src/getEff.ml 22 additions, 8 deletionssrc/getEff.ml
- src/getEff.mli 3 additions, 3 deletionssrc/getEff.mli
- src/global.ml 2 additions, 1 deletionsrc/global.ml
- src/lazyCompiler.ml 2 additions, 1 deletionsrc/lazyCompiler.ml
- src/licDump.ml 5 additions, 2 deletionssrc/licDump.ml
- src/licDump.mli 2 additions, 1 deletionsrc/licDump.mli
- src/main.ml 7 additions, 1 deletionsrc/main.ml
- src/split.ml 137 additions, 0 deletionssrc/split.ml
- src/split.mli 9 additions, 0 deletionssrc/split.mli
- src/test/test.res.exp 10260 additions, 1456 deletionssrc/test/test.res.exp
- src/unifyClock.ml 3 additions, 3 deletionssrc/unifyClock.ml
Loading
Please register or sign in to comment