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
Describe the bug
During recent debugging, I tried using dprint_tensix_dest_reg to check the value of the destination register before packing and discovered a bug.
My code performs a copy operation from an fp32 CB to another fp32 CB, with dprint_tensix_dest_reg inserted in between.
The values in the input and output CBs are identical, but the value printed by dprint_tensix_dest_reg differs from both the input and output.
After some debugging, I found that when constructing the float32 destination register value, it uses two 16-bit values. However, using the HEX() function to dprint the output revealed that the second 16-bit value is 0.
Describe the bug
During recent debugging, I tried using
dprint_tensix_dest_reg
to check the value of the destination register before packing and discovered a bug.My code performs a copy operation from an fp32 CB to another fp32 CB, with
dprint_tensix_dest_reg
inserted in between.The values in the input and output CBs are identical, but the value printed by
dprint_tensix_dest_reg
differs from both the input and output.After some debugging, I found that when constructing the float32 destination register value, it uses two 16-bit values. However, using the
HEX()
function to dprint the output revealed that the second 16-bit value is0
.You can found test related kernel code here:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
dprint_tensix_dest_reg
should be able to correctly print fp32 values.Screenshots
Please complete the following environment information:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: