Mercurial > hg > truffle
changeset 2572:28a8b3c8b9b4
Small fix to documentation.
| author | Thomas Wuerthinger <thomas@wuerthinger.net> |
|---|---|
| date | Mon, 02 May 2011 11:00:33 +0200 |
| parents | 95a9b8906b09 |
| children | 6d99b909696d |
| files | doc/design/graal_compiler.pdf doc/design/graal_compiler.tex |
| diffstat | 2 files changed, 1 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/design/graal_compiler.tex Mon May 02 10:56:35 2011 +0200 +++ b/doc/design/graal_compiler.tex Mon May 02 11:00:33 2011 +0200 @@ -192,7 +192,7 @@ \subsection{Frame States} Frame states capture the state of the program, in terms of the source representation (e.g., Java state: local variables, expressions, ...). -Whenever a safepoint is reached or \cwi{why is that an ``or'', both is basically the same} a deoptimization is needed a valid frame state needs to be available. +Whenever a safepoint is reached or \cw{why is that an ``or'', both is basically the same} a deoptimization is needed a valid frame state needs to be available. A frame state is valid as long as the program performs only actions that can safely be reexecuted (e.g., operations on local variables, etc.). Thus, frame states need only be generated for bytecodes that cannot be reexecuted: putfield, astore, invoke, monitorenter/exit, ...