-
Notifications
You must be signed in to change notification settings - Fork 12
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
d1774e0
commit f8a2278
Showing
5 changed files
with
41 additions
and
51 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
\subsubsubsection{Graphical representation \lispNone{}} \label{hub: instruction handling: call: generalities} \input{instruction_handling/call/generalities/lua/_inputs} | ||
\subsubsubsection{Universal constraints for \inst{CALL}'s \lispDone{}} \label{hub: instruction handling: call: generalities} \input{instruction_handling/call/generalities/universal} | ||
\subsubsubsection{First set of account-rows \lispDone{}} \label{hub: instruction handling: call: first set of account rows} \input{instruction_handling/call/generalities/account_rows_first_set} | ||
\subsubsubsection{Second set of account-rows \lispDone{}} \label{hub: instruction handling: call: second set of account rows} \input{instruction_handling/call/generalities/account_rows_second_set} | ||
\subsubsubsection{Third set of account-rows \lispDone{}} \label{hub: instruction handling: call: third set of account rows} \input{instruction_handling/call/generalities/account_rows_third_set} | ||
\subsubsubsection{Graphical representation \lispNone{}} \label{hub: instruction handling: call: generalities} \input{instruction_handling/call/generalities/lua/_inputs} | ||
\subsubsubsection{Universal constraints for \inst{CALL}'s \lispDone{}} \label{hub: instruction handling: call: generalities: universal} \input{instruction_handling/call/generalities/universal} | ||
\subsubsubsection{First set of account-rows \lispDone{}} \label{hub: instruction handling: call: generalities: first set of account rows} \input{instruction_handling/call/generalities/account_rows_first_set} | ||
\subsubsubsection{Second set of account-rows \lispDone{}} \label{hub: instruction handling: call: generalities: second set of account rows} \input{instruction_handling/call/generalities/account_rows_second_set} | ||
\subsubsubsection{Third set of account-rows \lispDone{}} \label{hub: instruction handling: call: generalities: third set of account rows} \input{instruction_handling/call/generalities/account_rows_third_set} |
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 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 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 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 |
---|---|---|
@@ -1,30 +1,29 @@ | ||
The present section presents vanishing constraints for columns that aren't used depeding on the instruction type. We \emph{may} impose that | ||
The present section presents vanishing constraints for columns that aren't used depending on the instruction type. We \emph{may} impose that | ||
\begin{description} | ||
\item[\underline{\inst{CREATE}-type instructions:}] \If $\isCreate_{i} = 1$ \Then | ||
\[ | ||
\left\{\begin{array}{lclr} | ||
\gasHi_{i} & = & 0 & (\trash) \\ | ||
\gasLo_{i} & = & 0 & (\trash) \\ | ||
\warm_{i} & = & 0 & (\trash) \\ | ||
\existence_{i} & = & 0 & (\trash) \\ | ||
\gasHi _{i} & = & 0 & (\trash) \\ | ||
\gasLo _{i} & = & 0 & (\trash) \\ | ||
\end{array}\right. | ||
\] | ||
\item[\underline{\inst{CALL} instructions:}] \If $\stpCall_{i} = 1$ \Then we impose nothing; | ||
\item[\underline{\inst{CALLCODE} instructions:}] \If $\stpCallCode_{i} = 1$ \Then we impose \( \existence_{i} = 1 \) | ||
\item[\underline{\inst{DELEGATECALL} instructions:}] \If $\stpDelegateCall_{i} = 1$ \Then | ||
\item[\underline{\inst{DELEGATECALL} and \inst{STATICCALL} instructions:}] | ||
\If $\stpDelegateCall _{i} + \stpStaticCall _{i} = 1$ | ||
\Then we impose | ||
\[ | ||
\left\{\begin{array}{lclr} | ||
\valHi_{i} & = & 0 & (\trash) \\ | ||
\valLo_{i} & = & 0 & (\trash) \\ | ||
\existence_{i} & = & 1 & (\trash) \\ | ||
\end{array}\right. | ||
\] | ||
\item[\underline{\inst{STATICCALL} instructions:}] \If $\stpStaticCall_{i} = 1$ \Then | ||
\[ | ||
\left\{\begin{array}{lclr} | ||
\valHi_{i} & = & 0 & (\trash) \\ | ||
\valLo_{i} & = & 0 & (\trash) \\ | ||
\valHi _{i} & = & 0 & (\trash) \\ | ||
\valLo _{i} & = & 0 & (\trash) \\ | ||
\end{array}\right. | ||
\] | ||
\saNote{} | ||
Recall that neither \inst{DELEGATECALL} nor \inst{STATICCALL} have a ``\texttt{value}'' argument. | ||
\item[\underline{Non \inst{CALL}, \inst{CALL}-type instructions:}] | ||
\If $\stpCallCode _{i} + \stpDelegateCall _{i} + \stpStaticCall _{i} = 1$ | ||
\Then we impose that | ||
\[ \existence _{i} = 0 \] | ||
\saNote{} | ||
We justify the choice to impose $\existence \equiv 0$ for non \inst{CALL}, \inst{CALL}-type instructions in | ||
section~(\ref{hub: instruction handling: call: generalities: universal}), | ||
specifically in (\ref{hub: instruction handling: call: generalities: universal: account existence for non CALLs}). | ||
\end{description} | ||
\ob{TODO: are these restrictions desirable ? These are obviously harmless constraints, they make for slighty smaller lookups if we segregate them by instruction type, and potentially add constraints if we don't.} |