You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I have encountered a bug where the NX (Inexact) bit in the fflags register fails to be set under certain microarchitectural conditions, specifically after clearing the fflags register(necessary) and then executing an operation that should simultaneously trigger both Overflow (OF) and Inexact (NX) exceptions. This behavior deviates from the expected IEEE 754 standard compliance.
Expected Behavior: fflags = 0x5 Actual Behavior: fflags = 0x4
Note:
This is a different issue from pulp-platform/fpu_div_sqrt_mvp#15, as they have different triggering conditions. The previous trigger method has already been fixed; now, we are facing a different new bug.
The text was updated successfully, but these errors were encountered:
youzi27
added
the
Type:Bug
For bugs in the RTL, Documentation, Verification environment or Tool and Build system
label
Apr 20, 2024
Is there an existing CVA6 bug for this?
Bug Description
Description
I have encountered a bug where the NX (Inexact) bit in the fflags register fails to be set under certain microarchitectural conditions, specifically after clearing the
fflags
register(necessary) and then executing an operation that should simultaneously trigger both Overflow (OF) and Inexact (NX) exceptions. This behavior deviates from the expected IEEE 754 standard compliance.Steps to Reproduce
Expected Behavior:
fflags = 0x5
Actual Behavior:
fflags = 0x4
Note:
This is a different issue from pulp-platform/fpu_div_sqrt_mvp#15, as they have different triggering conditions. The previous trigger method has already been fixed; now, we are facing a different new bug.
The text was updated successfully, but these errors were encountered: