Remove libc subsituation #450
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Based on the performance evaluation, the checking overhead of libc subsituation is larger than its performance improvement in most cases. Its effectiveness only displays in the specific cases, and it cannot be further optimized though JIT. Therefore, we decided to remove this mechanism.
jserv
reviewed
Jun 3, 2024
There was a problem hiding this comment.
Benchmarks
| Benchmark suite | Current: b8bb4b4 | Previous: ded6f04 | Ratio |
|---|---|---|---|
Dhrystone |
4.44 Average DMIPS over 10 runs |
4.37 Average DMIPS over 10 runs |
0.98 |
Coremark |
0.004 Average iterations/sec over 10 runs |
0.004 Average iterations/sec over 10 runs |
1 |
This comment was automatically generated by workflow using github-action-benchmark.
vestata
pushed a commit
to vestata/rv32emu
that referenced
this pull request
Jan 24, 2025
Remove libc subsituation
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the performance evaluation, the checking overhead of libc subsituation is larger than its performance improvement in most cases. Its effectiveness only displays in the specific cases, and it cannot be further optimized though JIT. Therefore, we decided to remove this mechanism.