Add docs/spec/fluidpop-isa.md ISA extension reference skeleton #117
Labels
No labels
adr
agent:blocked-ci
agent:blocked-human
agent:blocked-resolver
agent:done
agent:in-progress
agent:no-touch
agent:pinged
agent:pr-open
agent:queued
agent:wip
area:board
area:funding
area:infra
area:phy
area:poplink
area:rtl
area:software
area:supply-chain
area:verification
ci-failed
ci-timeout
docs
do-not-merge
human-approved
needs-human-approval
needs-rebase
needs-triage
phase:1
ready-for-review
review:findings
review:pass
risk:tripwire
swarm:quarantined
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Fluid/fluidpop-v1#117
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Goal
Create the ISA extension reference skeleton at
docs/spec/fluidpop-isa.md, listed as deliverable #3 in PLAN.md Section 10. The doc enumerates RoCC-routed instructions exposed byPopRoCCRouterto upstream Gemmini and any FluidPop-specific extensions, so RTL and software work share a single instruction inventory.Sections to include:
Acceptance criteria
docs/spec/fluidpop-isa.mdexists with the sections aboveStatus: Draft skeleton+Owner: TBDheaderTODOmarkers + 2-3 line intentPlan refs
Section 10 (deliverable #3), Section 8.2 (PopRoCCRouter custom module)
Notes
Skeleton only — actual ISA decisions belong in dedicated ADRs once PopRoCCRouter design solidifies. Avoid committing to specific custom opcodes; the doc's job is structure plus a clear open-questions list, not to specify the ISA.
Resolver inspection:
docs/spec/fluidpop-isa.mdalready exists onmain(introduced/extended via PR #77, commitf793b3d) and satisfies every acceptance criterion in this issue:Status: Draft skeleton+Owner: TBD(lines 6-7).> TODO.block with 2-3 line intent.TBDplaceholder row only.PopRoCCRouter) in the header.Issue #117 looks like a duplicate of the already-merged work. Recommend closing as duplicate of #77.