Skip to content

[hardware] fix latency stall bug in VMFPU - #482

Merged
hopang-0221 merged 2 commits into
mainfrom
fix/lat_stall
Aug 16, 2026
Merged

[hardware] fix latency stall bug in VMFPU#482
hopang-0221 merged 2 commits into
mainfrom
fix/lat_stall

Conversation

@Navaneeth-KunhiPurayil

@Navaneeth-KunhiPurayil Navaneeth-KunhiPurayil commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Fixed

  • Latency of some instructions were not specified leading to wrong results in the _blackscholes benchmark from rivec. When low latency operation/instruction follows a higher latency operation, it needs to be stalled for high latency operation to complete to avoid low latency operation results to be committed to VRF ahead of the higher latency operation into the wrong destination register.

Checklist

  • Automated tests pass
  • Changelog updated
  • Code style guideline is observed

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Navaneeth, can you explain why you use the latency_stall instead of the registered latency_stall_{d,q}? The same for vinsn_issue_lat and vinsn_processing_lat signals.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is because it is computed from an already registered signal vinsn_issue_q and vinsn_processing_q while previously it was using _d signals

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@hopang-0221
hopang-0221 merged commit 34bd3bc into main Aug 16, 2026
205 checks passed
@hopang-0221
hopang-0221 deleted the fix/lat_stall branch August 16, 2026 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants