Tracking legacy resolve train feature performance#823
Conversation
Change-Id: I9bb3f593b1e247977b371103fdd5ebb66821fcaa
|
🚀 Performance test triggered: gcc12-spec06-0.8c |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughConfiguration changes to KMHv3 examples: Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 1 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🚀 Coremark Smoke Test Results
✅ Difftest smoke test passed! |
|
[Generated by GEM5 Performance Robot] Ideal BTB PerformanceOverall Score
|
Change-Id: Ife75832bb85e5742ce3959b14eb9f32264036f70
|
Disable resolve train on kmhv3 evaluation: https://github.com/OpenXiangShan/GEM5/actions/runs/24229545486 |
🚀 Coremark Smoke Test Results
✅ Difftest smoke test passed! |
Change-Id: I9bb3f593b1e247977b371103fdd5ebb66821fcaa
Summary by CodeRabbit