Verilator

I haven't seen that internal error before; like other internal errors it should be impossible. If you have a test case I'll try to address it.

Here is test case that causes the same error. Please invoke verilator with -f verilator_cmd option. Thanks.

This is caused by the following in the memory wrappers

always @(posedge x) begin
  ...
  x = 0;
end

This isn't synthesizable and is confusing the ordering code. I thought I would be able to have a fix by now, but it's elusive, so I think this will have to remain unsupported (though with a better error message.)

This issue was resolved with a workaround.