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
circt-verilog has the following complaints when compiling the string.sv file:
string str;
^
s.sv:3:8: note: see current operation: %0 = "moore.variable"() <{name = "str"}> : () -> !moore.ref<string>
This error is due to MooreToCore's lack of string-type conversion. It only has StringConstantOpConv and Format*OpConversion; none of these conversions can handle the string type.
The text was updated successfully, but these errors were encountered:
Thanks for working on this, @Max-astro! HW doesn't have very good string support -- it's limited mostly to fixed-sized strings or strings that can be passed to module instances as parameter. There has been a recent effort in the Sim dialect, which collects simulation-related things, to come up with ways to do string formatting and representing format string literals. I think the Sim dialect would be a great place to add a type for dynamic strings such as Verilog's string type, and also have operations like concatenation, casting, and indexing. Maybe that would be a way forward for you?
I think the Sim dialect would be a great place to add a type for dynamic strings such as Verilog's string type, and also have operations like concatenation, casting, and indexing.
Thank you for your advice, I'll take a look at the Sim dialect and see if it's easy to add a dynamic string type.
I want to support this sv-tests-results/string_concat_op feature, but not sure how to fix it properly.
circt-verilog
has the following complaints when compiling the string.sv file:This error is due to MooreToCore's lack of string-type conversion. It only has
StringConstantOpConv
andFormat*OpConversion
; none of these conversions can handle thestring
type.The text was updated successfully, but these errors were encountered: