summaryrefslogtreecommitdiffstats
path: root/verilog.tex
diff options
context:
space:
mode:
authorYann Herklotz <git@yannherklotz.com>2020-07-06 10:14:30 +0100
committerYann Herklotz <git@yannherklotz.com>2020-07-06 10:14:30 +0100
commit0c106400728ab338f08384644a3daeae343d714a (patch)
tree87b375e19d58e67221715f088b83e1b47338df2f /verilog.tex
parent912cde654d071f603b5b27d219a025eb16166063 (diff)
downloadoopsla21_fvhls-0c106400728ab338f08384644a3daeae343d714a.tar.gz
oopsla21_fvhls-0c106400728ab338f08384644a3daeae343d714a.zip
Take away some comments
Diffstat (limited to 'verilog.tex')
-rw-r--r--verilog.tex2
1 files changed, 1 insertions, 1 deletions
diff --git a/verilog.tex b/verilog.tex
index 7b951c7..f11b6a2 100644
--- a/verilog.tex
+++ b/verilog.tex
@@ -93,7 +93,7 @@ We then define the semantics of running the module for one clock cycle in the fo
The \textsc{Module} rule is the main rule for the execution of one clock cycle of the module. Given that the value of the $s_{t}$ register is the value of the program counter at the current instruction and that the value of the $s_{t}$ register in the resulting association map is equal to the next program counter value, we can then say that if all the module items in the body go from one state to another, that the whole module will step from that state to the other.
-\input{verilog_notes}
+%%\input{verilog_notes}
%%% Local Variables:
%%% mode: latex