aboutsummaryrefslogtreecommitdiff
path: root/TODO
blob: aea5144c37e0ff64dbdd0d42e033cbfeb5917826 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
TODO 
   Figure out how types and widths propogate for all updated primops
   Write infer-types pass
   Update spec
      change concrete syntactical names of structural elements
      change direction names for bundle fields
      add new field for sequential or combinational
      play with non-implicit growth
      remove generics, add all combinations (adduu, addus, addss, ...)
      add assertions
      add convert to primop
      remove type from node in statement
   Future questions to address in spec:
      Introduction – motivation, and intended usage
      Philosophical justifications for all constructs
      More introduction for types, e.g. what is a ground type?
      What is a statement? What is an expression? What is a memory? Difference between vector type and memory? What are accessors for?
      Why would I ever write an empty statement? Mainly for use by compiler/passes
      What is a structural element? Duplication?
      Subtracting two unsigned numbers… Should talk to a math guy to figure it out
      What are shift left and shift right operations? HW doesn’t have these concepts. Need justification.
      What is lowered form? What is it for?


Tests:
   Error if declare anything other than module in circuit
   Error if incorrectly assign stuff, like use = instead of :=
   Error: Node not parsed for stmts