Skip to content

Conversation

@BKhristenko
Copy link
Collaborator

No description provided.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Adds a new Q (quad precision float) extension control and exposes its CSR bit in misa.

  • Introduces a MUTABLE_MISA_Q parameter to enable or disable mutability of the misa.Q bit.
  • Registers the Q field in arch/csr/misa.yaml with conditional read/write behavior based on the new parameter.
  • Implements field type, reset value, write legality, and constraint checks.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
arch/ext/Q.yaml Defines MUTABLE_MISA_Q parameter under extension schema
arch/csr/misa.yaml Adds Q CSR field with RW/RO logic, reset value, and legality checks
Comments suppressed due to low confidence (1)

arch/csr/misa.yaml:172

  • No tests were added or updated to verify the new MUTABLE_MISA_Q behavior and the Q CSR field; consider adding unit tests covering both mutable and immutable scenarios.
Q:

Copy link
Collaborator

@AFOliveira AFOliveira left a comment

Choose a reason for hiding this comment

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

There may be changes needed in F and D, but let's change only the comment I made and wait for upstream feedback

[when,"MUTABLE_MISA_Q == true"]
--
Indicates support for the `Q` (quad precision float) extension.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Let's switch this to " Writing 0 to this field will cause all quad-precision floating point instructions to raise an IllegalInstruction exception. "

Copy link
Collaborator

@AFOliveira AFOliveira left a comment

Choose a reason for hiding this comment

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

Maybe F and D will need updates but let's ask upstream folks opinion!

@AFOliveira AFOliveira merged commit 31cc426 into main May 22, 2025
12 checks passed
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.

3 participants