Wilson Snyder
Wilson Snyder
You suggest the way I would have done it. ;) In terms of how it's used it ideally would report differences based on these cases: - Signal added, or removed...
Correct.
For c++20 we need a configure error that can be overridden for at least a full release. Want to make that, or I can.
Does the linker (clang/gcc ld, mold) support -MD for determining dependent files?
I was also unable to find any automatic dependency detector for ld. So I don't think we can/should make some complicated check for finding library dependencies if user does e.g....
FWIW I always thought allowing '=' in general expressions was a bad idea in C and seemed unfortunate to propagate to SystemVerilog. When I use "always_comb" I get a multidriver...
The error itself passes on master as of some time ago, just added warning on this use of `=` when using `-Wall` or similar.
Next step after this works would be to remove the slicing, or at least for 'a=b' cases.
As you speculated, Verilator doesn't have any support for tristates through the API, so you are observing whatever behavior falls-out of the existing conversion from tristate to separate enable-based 2-state...
Are the interface instances "above" the hier split point, "crossing" it (which won't work as not supported - but you seem to say you're not doing this), or "below", or...