pc2 / pc2/sus-compiler

Resource usage reporting on hover

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue
Dominant language
Rust
Stars
126
Forks
6
PR merge metrics
No merged PRs in 30d

Description

We should estimate and report the amount of resources consumed by operations and wires. Resource counts for registers, LUTs, BRAMs and DSPs

Possibly those could even be subdivided further, like "LUT-bound registers" and "free registers"

  • Infrastructure. Compute and store this information in InstantiatedModule
  • Number of pipeline stages on top of wire
  • register resource count
  • LUT Count
  • Special resources, like BRAMs, MLABs, M20ks, DSPs

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating InstantiatedModule and the hover-reporting path, then trace how operations and wires are represented. Define how pipeline stages and counts for registers, LUTs, BRAMs, MLABs, M20ks, and DSPs should be computed and stored; done means these resource estimates appear on hover.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.