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
Now that the SSP dialect is starting to land, one potentially enhancement is to import/export CIRCT scheduling problems into and out of well-defined solver formats. For example, SAT problems have a CNF format, and SMT problems have SMT2 format, etc. This might not be directly useful for flows using CIRCT's scheduling library, but at least being able to export problems could open the door for such flows to kick out problems in a well-known format for solver researchers to experiment offline.
The text was updated successfully, but these errors were encountered:
+1 on the idea, though I wouldn't coin this as an import/export format from/to SSP. I think what you're describing is more like a "one-sided scheduler": 1) take a Problem instance, 2) construct a concrete ILP/SAT/SMT/... formulation, and 3) emit that in an appropriate native solver format. However, SSP makes it possible to do this in a small standalone tool (ssp-translate, anyone? 😉)
Now that the SSP dialect is starting to land, one potentially enhancement is to import/export CIRCT scheduling problems into and out of well-defined solver formats. For example, SAT problems have a CNF format, and SMT problems have SMT2 format, etc. This might not be directly useful for flows using CIRCT's scheduling library, but at least being able to export problems could open the door for such flows to kick out problems in a well-known format for solver researchers to experiment offline.
The text was updated successfully, but these errors were encountered: