chipsalliance / chipsalliance/rocket-chip
How about maintain a build.wake?
- Dominant language
- Scala
- Stars
- 3.9k
- Forks
- 1.3k
- Avg merge
- 5d 13m
- Merged PRs (30d)
- 1
Description
**Type of issue**: other enhancement
**Impact**: no functional change
**Development Phase**: proposal
**Other information**
The Wake script is a very good way to compose different design. Wake not only provide a method to compile Scala modules from source code, but also provide a way to compose different design parts to an integrated one. Wake provides many key concepts that apply to IC design flow, such as hash chain, file output chasing, differnt EDA flow integration. It is a much better solution than some other alternatives.
The IC industry needs not only a new RTL launguage, a new basic ISA, but also a unified EDA flow. A standard, input/output clearly, pure functional dependency, Wake-based flow is very important for the IC users to have a unified and sharable experience among different groups.
@davidmlw would offer to maintain a basic rocket-chip build.wake if the community is interested. @jackkoenig @terpstra @sequencer
Contributor guide
Research direction
The proposal is to add and maintain a basic build.wake for Rocket Chip, but it names no existing files, tests, or implementation steps. Start by reviewing the repository's current build flow and the Wake concepts described in the issue. Done would require an agreed scope and an accepted, maintainable build.wake.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100