Skip to content

Conversation

@ricted98
Copy link
Contributor

@ricted98 ricted98 commented Aug 28, 2025

These changes add support for FPU instructions in superscalar mode. The FPU requires a new top level signal to ease structural hazards detection, as detailed in openhwgroup/cvfpu#156.
Testing was done locally using embench-iot, however there is the open point of testing this feature in the CI.

@github-actions
Copy link
Contributor

❌ failed run, report available here.

4 similar comments
@github-actions
Copy link
Contributor

❌ failed run, report available here.

@github-actions
Copy link
Contributor

❌ failed run, report available here.

@github-actions
Copy link
Contributor

❌ failed run, report available here.

@github-actions
Copy link
Contributor

❌ failed run, report available here.

@ricted98 ricted98 force-pushed the rt/superscalar-fpu-support branch from 3281898 to 1be662d Compare October 13, 2025 09:30
@github-actions
Copy link
Contributor

❌ failed run, report available here.

1 similar comment
@github-actions
Copy link
Contributor

❌ failed run, report available here.

@ricted98 ricted98 force-pushed the rt/superscalar-fpu-support branch from 379b660 to 747ba84 Compare October 22, 2025 09:44
@ricted98
Copy link
Contributor Author

Marking this as ready for review after the merging of openhwgroup/cvfpu#156.

@ricted98 ricted98 marked this pull request as ready for review October 22, 2025 09:45
@ricted98
Copy link
Contributor Author

ricted98 commented Oct 22, 2025

One open point: currently no CI configuration tests the FPU support in the superscalar configuration.

@JeanRochCoulon
Copy link
Contributor

Hello @ricted98
Why not adding tests in GitHub Actions ?

@ricted98
Copy link
Contributor Author

Hi @JeanRochCoulon, I can of course add it. Would you like a new configuration to be pushed or should we just override cv32a65x for the tests?

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