projects
/
matthijs
/
master-project
/
report.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
951d8f0
)
Add some extra outline to the Hardware Description chapter.
author
Matthijs Kooijman
<matthijs@stdin.nl>
Fri, 30 Oct 2009 10:08:48 +0000
(11:08 +0100)
committer
Matthijs Kooijman
<matthijs@stdin.nl>
Fri, 30 Oct 2009 10:08:48 +0000
(11:08 +0100)
Chapters/Prototype.tex
patch
|
blob
|
history
diff --git
a/Chapters/Prototype.tex
b/Chapters/Prototype.tex
index e11788611fa6ab3ae827c3fd13a69602415d4368..644ce01ce4cf4e6629a80fc53958d4d7d789e98d 100644
(file)
--- a/
Chapters/Prototype.tex
+++ b/
Chapters/Prototype.tex
@@
-50,6
+50,9
@@
TODO: Was Haskell really a good choice? Perhaps say this somewhere else?
TODO: Was Haskell really a good choice? Perhaps say this somewhere else?
+ \subsection{Output language or format}
+ VHDL / Verilog / EDIF etc. Why VHDL?
+
\section{Prototype design}
As stated above, we will use the Glasgow Haskell Compiler (\small{GHC}) to
implement our prototype compiler. To understand the design of the
\section{Prototype design}
As stated above, we will use the Glasgow Haskell Compiler (\small{GHC}) to
implement our prototype compiler. To understand the design of the
@@
-710,9
+713,8
@@
fstint = λa.λb.fst @Int @Int a b
\subsection[sec:prototype:separate]{Separate compilation}
- Simplified core?
\subsection[sec:prototype:separate]{Separate compilation}
- Simplified core?
- Haskell language coverage / constraints
- Recursion
- Builtin types
- Custom types (Sum types, product types)
- Function types / higher order expressions
-
+ \section{Haskell language coverage and constraints}
+ Recursion
+ Builtin types
+ Custom types (Sum types, product types)
+ Function types / higher order expressions