[ImportVerilog] Allow functions to capture values from parent scope #9107
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch teaches the ImportVerilog conversion to detect and plumb captured references from enclosing scopes into lowered MLIR functions.
capturesandcaptureIndexto record refs captured from outer scopes.finalizeFunctionBodyCapturesto extend the function signature with capturedmoore::RefTypeinputs and replace their in-body uses with the new block arguments.convertFunctionnow installs a temporaryrvalueReadCallbackthat collects refs read from outside the function’s body.moore::RefTypevalues originating from the enclosing (module) region.Together these changes allow nested or free functions to reference module-level signals (
logic, etc.) correctly in the generated MLIR, with explicit function parameters modeling captured variables.