You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
axi_xbar_unmuxed doesn't parse with (our version of) Xcelium because of problems with multi dimensional interfaces. I see the same problem has come up with VCS which was fixed in 14fbbf5
Two thoughts here
My experience tells me that it's best to avoid multi-dimensional interfaces completely because of poor tool support
Use something like `ifdef NO_MULTI_DIM_ARRAYS instead of `ifdef VCS. It's not a good idea to have tool-specific ifdefs. It's better to name the ifdef after the actual missing feature (e.g. `ifdef NO_MULTI_DIM_ARRAYS in this case) I had the same comment a couple of years ago around assertions where there were a lot of `ifdef VERILATOR. When we wanted to run this in XSIM, we had to also add a layer of `ifdef XSIM and then after a while, Verilator started to support assertions which made things more confusing. Having e.g. an `ifdef ASSERTIONS and controlling when to set that through the build system would help in these cases.
The text was updated successfully, but these errors were encountered:
axi_xbar_unmuxed doesn't parse with (our version of) Xcelium because of problems with multi dimensional interfaces. I see the same problem has come up with VCS which was fixed in 14fbbf5
Two thoughts here
`ifdef NO_MULTI_DIM_ARRAYS
instead of`ifdef VCS
. It's not a good idea to have tool-specific ifdefs. It's better to name the ifdef after the actual missing feature (e.g.`ifdef NO_MULTI_DIM_ARRAYS
in this case) I had the same comment a couple of years ago around assertions where there were a lot of`ifdef VERILATOR
. When we wanted to run this in XSIM, we had to also add a layer of`ifdef XSIM
and then after a while, Verilator started to support assertions which made things more confusing. Having e.g. an`ifdef ASSERTIONS
and controlling when to set that through the build system would help in these cases.The text was updated successfully, but these errors were encountered: