Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RTL code coverage hole in CV32E40P lzc #1022

Open
YoannPruvost opened this issue Jul 10, 2024 · 1 comment
Open

RTL code coverage hole in CV32E40P lzc #1022

YoannPruvost opened this issue Jul 10, 2024 · 1 comment
Labels
Component:RTL For issues in the RTL (e.g. for files in the rtl directory) WAIVED:CV32E40P Issue does not impact a major release of CV32E40P and is waived

Comments

@YoannPruvost
Copy link
Contributor

YoannPruvost commented Jul 10, 2024 •
edited
Loading

Component

Component:RTL

Issue Description

The interconnect between the core and the FPU has been designed to handle multiple cores to multiple FPU connections. As the verification has been done with a one-core setup, the LZC used to arbitrate between different core is under-utilized and some part of the code is unreachable in this setup.

As it was too late to implement a different solution in RTL due to long RISC-V ISA Formal Verification runs and requiring to update all waivers files as well, it has been decided to waive those holes in v2.
@YoannPruvost YoannPruvost added Component:RTL For issues in the RTL (e.g. for files in the rtl directory) WAIVED:CV32E40P Issue does not impact a major release of CV32E40P and is waived labels Jul 10, 2024
@MikeOpenHWGroup
Copy link
Member

Hi @YoannPruvost, can you provide some addition insight into this code coverage hole?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Component:RTL For issues in the RTL (e.g. for files in the rtl directory) WAIVED:CV32E40P Issue does not impact a major release of CV32E40P and is waived
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@MikeOpenHWGroup @YoannPruvost