Fix a couple of bugs in the -oite option.
- predef Lustre op were declared as memoryful. - expr like "if true then ..." were badly translated - The clock and types of some expressions created by L2lOptimIte had a bad arity (in presence of tuples) - in order to perform the -oite optim, also check that each branch is safe.
Showing
- src/l2lOptimIte.ml 32 additions, 14 deletionssrc/l2lOptimIte.ml
- src/l2lSplit.ml 13 additions, 4 deletionssrc/l2lSplit.ml
- src/lic.ml 1 addition, 1 deletionsrc/lic.ml
- src/licEvalType.ml 3 additions, 3 deletionssrc/licEvalType.ml
- src/lv6MainArgs.ml 5 additions, 3 deletionssrc/lv6MainArgs.ml
- src/lv6version.ml 2 additions, 2 deletionssrc/lv6version.ml
- test/lus2lic.sum 14 additions, 12 deletionstest/lus2lic.sum
- test/lus2lic.time 9 additions, 7 deletionstest/lus2lic.time
- test/should_work/carV2.lus 11 additions, 8 deletionstest/should_work/carV2.lus
- test/should_work/heater_control.lus 8 additions, 8 deletionstest/should_work/heater_control.lus
Loading
Please register or sign in to comment