Open David-Durst opened 5 years ago
This may be a verilator problem rather than a fault problem, I'm not sure if fault can do anything about this.
Can you check if the module Reduce_S_n4_opNativeMapParallel_n1_opAdd_Atom_I_Tuple_0_Array_8_In_Bit___1_Array_8_In_Bit____O_Array_8_Out_Bit____I_Array_1_Tuple_0_Array_8_In_Bit___1_Array_8_In_Bit_____O_Array_1_Array_8_Out_Bit____
is indeed present in the output verilog files? If not, it may be an issue with the module naming rewriting logic
Doesn't verilator have issues with double underscores in names? Try removing all consecutive underscores and seeing if that helps.
Yea, we try to handle that with https://github.com/leonardt/fault/blob/master/fault/verilog_utils.py#L23-L28 where double underscores are replaced with ___05F, but there may be a place where we're missing this logic
https://github.com/David-Durst/aetherling/blob/185c5cf0ef85845b29ebf5f30912520c0c267a49/tests/test_space_time/test_reduce.py#L28-L46 passes.
However, it fails if you remove the call to
wrap_module_with_top
, which just wraps the module with one whose name is "top"The failure message is that it can't find the top module. I believe this is because the name is too long. The error message is below