Closed vogelpi closed 6 months ago
Thank you for filing this issue! Indeed sv2v was using the wrong byte order. This should be fixed as of 81d822562a490051d93fed4557b4e841476259c8. Can you try it out?
Fantastic! Many thanks @zachjs for the quick fix! I've tested the latest version and it works as expected.
Hi @zachjs , I just noticed an issue that seems to have been introduced somewhere between version 0.0.9-24 and current 0.0.11 (I know there has been quite some time and work in between, sorry). Namely, it seems that newer versions convert a width extended string e.g.
64'("GA")
into an integer64'("16711")
(== 64'h4147
) where previous versions would just leave64'("GA")
.This can be an issue when later during synthesis (e.g. using Yosys) a string parameter is compared against this integer. Because the string "GA" in synthesis is converted to
16'01000111_01000001
(== 16'h4741), i.e., the bytes are in the opposite order. The string won't match.I give you a minimal code snippet:
With sv2v-0.0.9-24:
and with sv2v-0.0.11: