diff options
| author | Xavier Leroy <xavierleroy@users.noreply.github.com> | 2018-06-17 17:48:01 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-06-17 17:48:01 +0200 |
| commit | 7a5aef7aa4b669a722ecce3da6e7f7c646a392cc (patch) | |
| tree | 5f50db9ea90cc8ca55551f364d972d134c3f9177 /doc/index.html | |
| parent | 3d348f51e343ff84b8e550fbeb905e23bf2b6175 (diff) | |
| download | compcert-7a5aef7aa4b669a722ecce3da6e7f7c646a392cc.tar.gz compcert-7a5aef7aa4b669a722ecce3da6e7f7c646a392cc.zip | |
Treat Outgoing stack slots as caller-save in LTL/Linear semantics (#237)
* Outgoing stack slots are set to Vundef on return from a function call,
modeling the fact that the callee could write into those stack slots.
(CompCert-generated code does not do this, but code generated by other
compilers sometimes does.)
* Adapt Stackingproof to this new semantics. This requires tighter
reasoning on how Linear's locsets are related at call points and
at return points.
* Most of this reasoning was moved from Stackingproof to Lineartyping,
because it can be expressed purely in terms of the Linear semantics,
and tracked through the wt_state predicate.
* Factor out and into Conventions.v: the notion of callee-save
locations, the "agree_callee_save" predicate, and useful lemmas on
Locmap.setpair. Now the same "agree_callee_save" predicate is used
in Allocproof and in Stackingproof.
Diffstat (limited to 'doc/index.html')
0 files changed, 0 insertions, 0 deletions