Need better error reporting for pin count mismatches in the .arch file about vtr-verilog-to-routing

[kmurray]

Agreed.  Architecture file error reporting has been pretty bad in general.  I've put
in a bunch more meaningful error messages, with line numbers, and some array bounds
checking as well (in addition to the case listed here).  Debugging an architecture
file is still painful but should be much easier now.

I expect there's still stuff that I missed that would make it easier to catch malformed
architecture files.  Let me know if you find any that you would like fixed.

As future work, it will be nice to upgrade graphics to allow a user to look into a
complex block.  Makes it easier to check if things are built the way the user expected.

Reported by JasonKaiLuu on 2012-06-04 16:21:17

• Status changed: Fixed

[kmurray]

Thanks Jason.  The graphics idea is a good one.

Vaughn

Reported by vaughnbetz on 2012-06-04 17:01:01