Closed dillonhuff closed 4 years ago
@dillonhuff That first one should absolutely be legal. The issue unfortunately looks like there are two distinct CoreIR contexts being created and used (C++ objects representing CoreIR types are constructed in CoreIR context). Can you make sure that only a single context is ever being created in your flow? If you think you are doing this, can I get a quick summary of the code?
It could also easily be related to https://github.com/rdaly525/coreir/issues/929. Are you using the latest CoreIR which has the assertion added in https://github.com/rdaly525/coreir/pull/930
@rdaly525 it was the double context issue. I don't know what version I'm on.
@rdaly525 I'm working on getting some code for the ASPLOS ubuffer paper working and I get the following error while wiring up some coreir modules:
When I flip the type of
rst_n
onself
I get the error:Am I misunderstanding the meaning of type directions in coreir? I assumed at least one of these combinations must be legal.