RAM configurations should propagate scheduling constraints
Open
enhancement
scheduler
- Dominant language
- C++
- Stars
- 1.9k
- Forks
- 283
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 135
Description
RAM configuration includes latency information, but this is not propagated to the scheduler and a separate, matching scheduling constraint must be added manually. The sram configuration should add the scheduling constraint to avoid this duplication.
Contributor guide
Assessment
This issue has not been assessed yet.