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
I added attributes to debug variable to store the chisel type name and, eventually, the constructor parameters in the debug dialect (and maybe in dbg.struct and dbg.array as well).
However, I may need to create a dbg variable for each sub field, recursively, of aggregates.
Is there a reason why values in dbg.struct/dbg.array are of Firrtl types rather than dbg.variable type in MaterializeDebugInfo?
The text was updated successfully, but these errors were encountered:
I think we can to expose the chisel type via compiler plugin like what we did in the source info. But what on earth is a chisel type? That’s the fundamental question(we need specification)
I think we can to expose the chisel type via compiler plugin like what we did in the source info.
I already managed to expose source level information from chisel to firrtl and firtool. In the meantime I also managed to read this information from firtool, processing it into proper debug variables and updating hgldd/emitting a new file format.
But what on earth is a chisel type? That’s the fundamental question(we need specification)
Whit chisel type refer to the type of the scala variable in the source chisel code.
In the following example:
@fabianschuiki I created this issue to keep talking about the conversation we started here: chipsalliance/chisel#4015 (comment)
I added attributes to debug variable to store the chisel type name and, eventually, the constructor parameters in the debug dialect (and maybe in
dbg.struct
anddbg.array
as well).However, I may need to create a dbg variable for each sub field, recursively, of aggregates.
Is there a reason why values in
dbg.struct
/dbg.array
are of Firrtl types rather thandbg.variable
type inMaterializeDebugInfo
?The text was updated successfully, but these errors were encountered: