-
Notifications
You must be signed in to change notification settings - Fork 298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SCFToCalyx] Memory banking for Calyx #7671
base: main
Are you sure you want to change the base?
Conversation
This should be done using attributes on memories. An extra JSON file that lives separate from the source program seems unnecessary |
I agree, and I have thought of that, too. The cons are users have to go to the source And I'd appreciate it if anyone could let me know that attribute insertion can be automated. |
Attributes can be automatically inserted by frontends. |
That's great! And just removed the needs for passing JSON and now only relies on attributes on memory allocations |
Cool! Can you add tests and fix the failures? I can review it then and we can merge after the review. |
Breaking down #7409
This patch will support memory banking in Calyx by user specifying the number of available banks for each memory (in the order they are declared in the source
.mlir
file) in ajson
file