-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
371d9c7
commit 2bffe04
Showing
6 changed files
with
17 additions
and
30 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
\subsection{Memory continuations} | ||
\label{mem-continuations} | ||
|
||
The MemBefore (resp. MemAfter) table holds the content of the memory before (resp. after) the execution of the current segment. | ||
For consistency, the MemAfter trace of a segment must be identical to the MemAfter trace of the next segment. | ||
Each row of these tables contains: | ||
|
||
\begin{enumerate} | ||
\item $a$, the memory cell address, | ||
\item $v$, the initial value of the cell. | ||
\end{enumerate} | ||
The tables should be ordered by $(a, \tau)$. Since they only hold values, there are no constraints between the rows. | ||
|
||
A CTL copies all of the MemBefore values in the memory trace as reads, at timestamp $\tau = 0$. | ||
Another CTL copies the final values from memory to MemAfter. For more details on which values are propagated, consult \ref{final-memory}. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file not shown.