Skip to content

[PyCDE/CAPI] iverilog chokes on automatic logic #3696

Open
@mortbopet

Description

automatic logic can be circumvented by passing --lowering-options=disallowLocalVariables during --export-verilog.

For PyCDE, We'd want to be able to - at some point in the stack - to specify this variable. One point could be as a flag at the CAPI level:

m.def("export_verilog", [](MlirModule mod, py::object fileObject) {
circt::python::PyFileAccumulator accum(fileObject, false);
py::gil_scoped_release();
mlirExportVerilog(mod, accum.getCallback(), accum.getUserData());
});

As long as it is something which we can set when emitting RTL for @cocotestbench PyCDE runs.

Metadata

Assignees

No one assigned

    Labels

    PyCDEPython CIRCT Design Entry API

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions