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

The UF flag in the fcsr register is different #3954

Open
5 tasks done
fly-1011 opened this issue Nov 28, 2024 · 2 comments
Open
5 tasks done

The UF flag in the fcsr register is different #3954

fly-1011 opened this issue Nov 28, 2024 · 2 comments
Labels
answered question Question requiring answer

Comments

@fly-1011
Copy link

Before start

  • I have read the RISC-V ISA Manual and this is not a RISC-V ISA question. 我已经阅读过 RISC-V 指令集手册,这不是一个指令集相关的问题。
  • I have read the XiangShan Documents. 我已经阅读过香山文档。
  • I have searched the previous issues and did not find anything relevant. 我已经搜索过之前的 issue,并没有找到相关的。
  • I have searched the previous discussions and did not find anything relevant. 我已经搜索过之前的 discussions,并没有找到相关的。
  • I have reviewed the commit messages from the relevant commit history. 我已经浏览过相关的提交历史和提交信息。

Describe the question

describe

When I was testing Xiangshan, when executing the following test sample, there would be inconsistencies in the fcsr register, specifically the UF flag.

Log screenshot

The inconsistent information between nemu and spike is as follows
image
image
image

Test samples and log information:fcsr.zip

Version Information

xiangshan:commit b00d582 (HEAD -> master, origin/master, origin/HEAD)
ready-to-run:commit 457f091898b2bcd26c8f6e983f3df174f990af43 (HEAD -> master, origin/master, origin/HEAD)

I also noticed that there seems to be a fix for the OF and UF flags in the yunsuan module(OpenXiangShan/YunSuan@548dbea), but the Xiangshan version I use has already been merged.

@fly-1011 fly-1011 added the question Question requiring answer label Nov 28, 2024
@HeiHuDie
Copy link
Collaborator

xiangshan: edb1dfa
ready-to-run: c1dc496545b9d62bb10264cd4485cb6fe7c60798
YunSuan: 2cafaa74daf43e2693bca80093a0af22678616a3
Sorry,I cannot reproduce this bug on the latest version of XiangShan.
I think this may be a problem caused by a certain version not matching.
屏幕截图 2024-11-28 135556

@fly-1011
Copy link
Author

Thank you for your reply. I will update to the latest version and conduct the testing again. I am also looking forward to the update of the yunsuan module being merged into Xiangshan. Thank you again😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered question Question requiring answer
Projects
None yet
Development

No branches or pull requests

2 participants