[eacsl] Use `toplevel_predicate` in `Translate.translate_predicate`
The function `Translate.translate_predicate` is meant to translate the root predicate of an assertion, so it makes sense to use `toplevel_predicate` as a parameter and it gives access to the `predicate_kind`. The loop invariants in `Env` are also stored as `toplevel_predicate` to facilitate the translation.
Showing
- src/plugins/e-acsl/src/code_generator/contract.ml 16 additions, 30 deletionssrc/plugins/e-acsl/src/code_generator/contract.ml
- src/plugins/e-acsl/src/code_generator/env.ml 1 addition, 1 deletionsrc/plugins/e-acsl/src/code_generator/env.ml
- src/plugins/e-acsl/src/code_generator/env.mli 2 additions, 2 deletionssrc/plugins/e-acsl/src/code_generator/env.mli
- src/plugins/e-acsl/src/code_generator/loops.ml 1 addition, 1 deletionsrc/plugins/e-acsl/src/code_generator/loops.ml
- src/plugins/e-acsl/src/code_generator/loops.mli 1 addition, 1 deletionsrc/plugins/e-acsl/src/code_generator/loops.mli
- src/plugins/e-acsl/src/code_generator/translate.ml 3 additions, 4 deletionssrc/plugins/e-acsl/src/code_generator/translate.ml
- src/plugins/e-acsl/src/code_generator/translate.mli 5 additions, 1 deletionsrc/plugins/e-acsl/src/code_generator/translate.mli
- src/plugins/e-acsl/src/code_generator/translate_annots.ml 3 additions, 3 deletionssrc/plugins/e-acsl/src/code_generator/translate_annots.ml
Loading
Please register or sign in to comment