Add cppyy Runtime Code Generation Target for Brian2 #1674
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.
Problem
The current Brian2 code generation pipeline suffers from a fundamental performance bottleneck. The issue is not tied to the specific tools we use, but rather to the Ahead-of-Time (AOT) compilation paradigm itself.
Regardless of whether we use Cython (our current approach) or manual C-extensions, the workflow remains slow and cumbersome:
In other words, the bottleneck lies in the file-based, external-compiler, AOT workflow.
Proposed Solution: JIT Compilation with
cppyy
This PR introduces
cppyy
as a new runtime code generation target, shifting from AOT to Just-in-Time (JIT) compilation.With
cppyy
, C++ code is compiled in-memory using the Cling C++ interpreter, which eliminates:Current Status
Implemented and functional in this initial proof of concept:
Next Steps
This PR serves as a starting point and contains some hardcoded components that will be refined in future iterations. A follow-up issue will be created to present the detailed roadmap and outline how we plan to transition from this POC to a fully integrated solution for Brian2 :)