aboutsummaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorazidar2015-06-12 21:14:08 -0700
committerazidar2015-06-12 21:14:08 -0700
commite52a3a2be22648a964bea9e06d6f0c64938ea116 (patch)
treee548bcab8fd057033883e5d23ec1335876fe07c5 /TODO
parenta1141295b939f2066186c96791bfd64e19209478 (diff)
Added more changes to spec
Diffstat (limited to 'TODO')
-rw-r--r--TODO24
1 files changed, 17 insertions, 7 deletions
diff --git a/TODO b/TODO
index 6c343dcf..e036ab26 100644
--- a/TODO
+++ b/TODO
@@ -37,22 +37,29 @@ Checks:
widths are -1 of size
zero width?
-
======== Update Core ==========
Add bi-accessor
-Add readwriteport
+Add RdWrPort
+Add SubwordConnect
+Add clock, reset to reg
+Add clock to cmem, smem
+Add clock to Direction, make sure it all works
+Remove concrete syntax from EmptyStmt()
======== Check Passes ==========
High-Firrtl
No combinational loops
+ Clocks are used correctly
+ Restrictions on subword assignments
+
After adding dynamic assertions, insert bounds check with accessor expansion
Width inference
No names
No Unknowns
- All widths are positive
+ All widths are positive, and nonzero
Pad's width is greater than value's width
pad's width is greater than value's width
- connect can connect from big to small??
+ connect can connect from big to small?? <- I think this shouldn't be allowed
Width pad check?
======== Other Passes ========
@@ -80,11 +87,14 @@ Convert to scala
Firrtl interpreter (in scala)
======== Update Spec ========
-add printfs
-think about subword on accessors
+Add explanation of an instance type, ie converting from input/output to default/reverse
+ also, can only be used on the right side of :=
+Add assert statement explanation
+think about printfs
+think about subword on accessors, non-ground types
think about mems in lowered form - change ReadPort's reference to mem to be either exp or id
-add explanation about mems
think about ROMS
+think about how widths propagate - add section explicitly addressing this
FIRRTL rule: No name can be a prefix of any other name.
Future questions to address in spec: