backends
=======
1. backends/firrtl/firrtl.cc – skipped because of error:
 ERROR: Unclocked write port 0 on memory top.ram.
Add model with memory block too, so you can cover line block starting at
line 419

simple
=========
+ 1. passes/techmap/attrmap.cc
There is example in help block create example with
(* keep="true" *) attribute and run example

+ 2. passes/techmap/dff2dffe.cc
execute with  -unmap parameter

+ 3. passes/techmap/dff2dffs.cc

+ 4. passes/techmap/extract.cc
Lot of variations of input parameters is not excersised

? 5. passes/techmap/extract_counter.cc
This is specific to greenpak4 architecture, but idea is to have counter
in design and call this after synth_greenpak

+ 6. passes/techmap/shregmap.cc.
This also seams to be greenpak4 specific, but extracting shift register

misc
========
1. passes/techmap/insbuf.cc

Testing problems:
1. backends/firrtl/firrtl.cc – skipped because of error:
 ERROR: Unclocked write port 0 on memory top.ram.
Add model with memory block too, so you can cover line block starting at
line 419
2.dff2dffe -direct - skipped: ERROR: Found error in internal cell
\dffe.$procdff$47 ($dffe) at
3.insbuf -buf $_BUF_ in out - skipped: ERROR: Found error in internal
cell

MISC
=====
Tasks in this group are just generating some output, so no traditional
test bench could be made. Writing output from yosys and checking if
result is expected is advised.

1.http://scratch.clifford.at/coverage_html/passes/tests/test_abcloop.cc.gcov.html
This represents some internal tests for ABC loops
2.
http://scratch.clifford.at/coverage_html/passes/tests/test_cell.cc.gcov.html
note that you need to provide multiple tests in order to cover testing
of all cell types. Also output should be checked if it contain "Fail" or
"Error" in it
3.
http://scratch.clifford.at/coverage_html/passes/cmds/torder.cc.gcov.html
Use some verilog file, do proc and this should display you all cells in
designed ordered. Require multiple different parameters to cover all.
4.http://scratch.clifford.at/coverage_html/passes/cmds/trace.cc.gcov.html
loading verilog file and doing  "trace proc" will create output with
additional logs, not much to check from output to be honest
5.
http://scratch.clifford.at/coverage_html/passes/cmds/write_file.cc.gcov.html
just write to file and check if written output is fine
6.
http://scratch.clifford.at/coverage_html/passes/cmds/stat.cc.gcov.html
if you have liberty cell library files, try it with those specified.
7.
http://scratch.clifford.at/coverage_html/passes/cmds/show.cc.gcov.html
note that you would always need to set -viewer since you do not wish to
call graphwiz.
Need covering of various parameters on a reasonable complicated design
to cover.
8. http://scratch.clifford.at/coverage_html/passes/cmds/scc.cc.gcov.html
detection of logic loops, output needs to be tested in order to check if
loop was detected on not.
9.
http://scratch.clifford.at/coverage_html/passes/cmds/scatter.cc.gcov.html
After doing synth on existing design, just run this step, can do
opt_clean after and there should be lot of temporary and unused wires
removed.
10.
http://scratch.clifford.at/coverage_html/passes/cmds/rename.cc.gcov.html
can load design and rename top modue, output should contain module with
new name
11.
http://scratch.clifford.at/coverage_html/passes/cmds/qwp.cc.gcov.html
Use it on simple design since it takes a while on big ones.
12.
http://scratch.clifford.at/coverage_html/passes/cmds/ltp.cc.gcov.html
Check if returns expected value for your design
13.
http://scratch.clifford.at/coverage_html/passes/cmds/edgetypes.cc.gcov.html
it just outputs report, so not sure what would be valid to check, just
execute for now.
14.
http://scratch.clifford.at/coverage_html/passes/cmds/delete.cc.gcov.html
load existing design and try removing inputs, outputs,... complete
design
15.
http://scratch.clifford.at/coverage_html/passes/cmds/cover.cc.gcov.html
it just prints report, so nothing to check

 add tests for synth_anlogic and 'regression';  Megre commit: "Fix tests according to latest yosys and proper...

Merge commit "Fix tests according to latest yosys and proper gitignore
files".
Make the same changes for 'regression'.

1. Add tests for synth_anlogic command
Now this tests are commented because of:
+ iverilog -o testbench ../testbench.v synth.v ../../common.v
../../../../../techlibs/common/simcells.v
../../../../../techlibs/anlogic/cells_sim.v
../../../../../techlibs/anlogic/cells_sim.v:20: error: Unable to bind
wire/reg/memory `A' in `testbench.uut._09_'
../../../../../techlibs/anlogic/cells_sim.v:20: error: Unable to
elaborate r-value: (INIT)>>(A)
2 error(s) during elaboration.

2. Add 'regression' test

Add tests for "II architecture" and "III backends" and "IV frontends"

IV frontends
=============

For frontends idea is that you do not do read_verilog but some you are
reading input in different format.
Since most of formats yosys can also read and write you can use plain
verilog write blif for example
and use that as source for this coverage. For liberty files many
examples can be found so that is also in list of tasks

1.
http://scratch.clifford.at/coverage_html/frontends/blif/blifparse.cc.gcov.html
2.
http://scratch.clifford.at/coverage_html/frontends/ilang/ilang_frontend.cc.gcov.html
3.
http://scratch.clifford.at/coverage_html/frontends/json/jsonparse.cc.gcov.html
4.
http://scratch.clifford.at/coverage_html/frontends/liberty/liberty.cc.gcov.html

Signed-off-by: Clifford Wolf <clifford@clifford.at>

I simple

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

First tests for pilot project

5. clk2fflogic (104 - 144,180-195 are not covered)
9. memory_nordff(75-101 is not covered)
10. memory_unpack(91-108 is not covered)
12. hierarchy (the coverage from 44% increased to 61,3%)

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>

Signed-off-by: Clifford Wolf <clifford@clifford.at>