-
Notifications
You must be signed in to change notification settings - Fork 111
do_nop
is not negligible
#177
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
Comments
qwe661234
pushed a commit
to qwe661234/rv32emu
that referenced
this issue
Aug 4, 2023
1. Refine origin fused instruction by skipping insturction nop and correctly updating value to register. 2. Add new fused insturction lui + addi. Benchmark dhrystone gains about 3% performance improvement base on this modification. Close: sysprog21#177
jserv
pushed a commit
that referenced
this issue
Aug 4, 2023
This commit refines the macro fused instruction by skipping the "nop" instruction and ensuring proper value updates to the register. Additionally, it introduces a new fused instruction, lui + addi. As a result of these modifications, the Dhrystone benchmark experiences approximately a 3% performance improvement. Close #177 Co-authored-by: Yen-Fu Chen <[email protected]>
vestata
pushed a commit
to vestata/rv32emu
that referenced
this issue
Jan 24, 2025
This commit refines the macro fused instruction by skipping the "nop" instruction and ensuring proper value updates to the register. Additionally, it introduces a new fused instruction, lui + addi. As a result of these modifications, the Dhrystone benchmark experiences approximately a 3% performance improvement. Close sysprog21#177 Co-authored-by: Yen-Fu Chen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
do_nop
appears to consume some CPU cycles according to perf report. It is generated by macro operation fusion, and we should aim to eliminate its overhead as early as possible.Reproduce:
perf report -g
and be aware of the percentage ofdo_nop
.The text was updated successfully, but these errors were encountered: