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
Probably only thing we need in addition to chisel-circt and emit a bunch of DontTouches for CustomFileEmission (and make chisel-circt support annotation files)
Longer term we have the standard native binary distribution problem
[kevin] chiseltest with custom (e.g. SiFive) frontend flow
Adam said that SiFive has custom frontend flow, and thus cannot use chiseltest
Ideally we would add some infrastructure to chisel3 that allows users to define custom frontend flows that generate the circuit object (the scala instance inheriting from RawModule) and the LoFirrtl.
I’m proposing adding a ChiselTestStage and ScalaTest/Utest depending on it.
conclusion: don’t worry about this for now, SiFive only might want to use chiseltest for unittesting, so we do not need to run the custom stage for now
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
2021-08-16/17
Outreach
Updates
Pinned Items
*
Discussion 1
Elaborate and toLowFirrtl
Discussion 2
hasId.toTarget
->Target
(after entire transform renames)Data.toTarget
, which is String,Beta Was this translation helpful? Give feedback.
All reactions