-
Notifications
You must be signed in to change notification settings - Fork 665
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.
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
[TASK] Cascade CPU fuzzing research bugs track #1573
Comments
Thank you for the work done on CVA6 !! I like it! |
@acaldaya Would you be available to present the results in cva6 verification meeting ? it is scheduled at 2pm CET on Thursday @ASintzoff moderates it |
Sorry for the confusion, it is not my research, but really interested.
I will write to the authors and let them know about this thread. According
to the paper, a C1 fix was merged, but I didnt find a ref of it.
…On Thu, Oct 26, 2023, 07:55 JeanRochCoulon ***@***.***> wrote:
@acaldaya <https://github.com/acaldaya> Would you be available to present
the results in cva6 verification meeting ? it is scheduled at 2pm CET on
Thursday
@ASintzoff <https://github.com/ASintzoff> moderates it
—
Reply to this email directly, view it on GitHub
<#1573 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3FKZ6CFX6II7SMKUADIE3YBH3OTAVCNFSM6AAAAAA6P6JG62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBQGQ3DAMRWGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@flaviens Would you be available to present the work results ? |
Hello, thank you for your interest! I would like to underline that all the bugs were reported to you many months before the paper went public, in accordance with responsible disclosure. Here are some links to help you. openhwgroup/cvfpu#72 openhwgroup/cvfpu#73 Regarding the presentation, I must unfortunately decline for this specific time slot (this is a very short notice!). Kind regards, |
Additionally, @KatCe suggested that you may be interested in this issue (Y1) as well, despite being seemingly a yosys-related issue. |
Is there an existing CVA6 task for this?
Task Description
Recently the paper: Cascade: CPU Fuzzing via Intricate Program Generation showcased some bugs of the CVA6. The goal of this issue is to track which bugs have been fixed and the corresponding PR.
Required Changes
When a bug of the table is fixed, please link this issue with the corresponding bug ID or CVE in the PR.
Current Status
It is not straightforward to know if the bugs are already fixed.
Risks
No response
Prerequisites
No response
KPI (KEY Performance Indicators)
No response
Description of Done
When all bugs have been fixed and the status column is updated with the corresponding PR.
Associated PRs
No response
The text was updated successfully, but these errors were encountered: