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.

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

[BUG] Fails to Trigger Illegal Instruction Exception for some illegal Instructions #1967

Closed
1 task done
youzi27 opened this issue Mar 28, 2024 · 4 comments
Closed
1 task done
Labels
Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system

Comments

@youzi27
Copy link

youzi27 commented Mar 28, 2024

Is there an existing CVA6 bug for this?

  • I have searched the existing bug issues

Bug Description

Describe the bug:
The CVA6 does not trigger an illegal instruction exception when encountering the illegal instruction like '0x5162e55b'. This issue is reminiscent of the previously reported issue #1953 . Despite switching to a newer version of the core (commit: f73724b), the problem persists for certain instructions, including ‘0x5162e55b’. In addition, there are the instructions mentioned in issue #1966.

Expected behavior:
Upon encountering an illegal instruction, such as ‘0x5162e55b’, the CVA6 core is expected to trigger an illegal instruction exception.

The log is as follows

core   0: 0x0000000080002020 (0x5162e55b) unknown
@youzi27 youzi27 added the Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system label Mar 28, 2024
@JeanRochCoulon
Copy link
Contributor

Thnak you for this feedback. If I understand this bug was already detected and reported in #1953 and #1966, why to create a new GitHub issue. Do I misunderstand ?

@youzi27
Copy link
Author

youzi27 commented Mar 28, 2024

Hi @JeanRochCoulon ,

It was only after reviewing the CVA6 source code that I discovered the root cause. Therefore, I've created this issue to indicate that the latest version of CVA6 still has the problem described in issue #1953. I will submit a list of illegal instructions as comprehensive as possible later on to better address the decoding issue.

I apologize for any inconvenience this may have caused.

@JeanRochCoulon
Copy link
Contributor

I like getting feedbacks on CVA6 implementation, so let's go on with your work and contributions.
When a github issue is open, it means that it is not fixed. When someone fixes it, we close the Github issue.
That is why I would ask you to comment the existing Github issues (is needed), and close the current one. Thanks !

@youzi27
Copy link
Author

youzi27 commented Mar 28, 2024

Thank you for your encouraging response. I appreciate the clarity regarding the Github issue management process and will follow your guidance by commenting on the existing issues as needed and closing the current one. Thanks again for your support!😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type:Bug For bugs in the RTL, Documentation, Verification environment or Tool and Build system
Projects
None yet
Development

No branches or pull requests

2 participants