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

chacha: Remove optimized code path for Silvermont-like CPUs. #2327

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

briansmith
Copy link
Owner

This makes CPU feature detection simpler and helps the code coverage testing effort.

@briansmith briansmith self-assigned this Feb 4, 2025
Copy link

codecov bot commented Feb 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.58%. Comparing base (509008b) to head (4523def).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2327      +/-   ##
==========================================
- Coverage   96.58%   96.58%   -0.01%     
==========================================
  Files         175      175              
  Lines       21490    21478      -12     
  Branches      513      512       -1     
==========================================
- Hits        20756    20744      -12     
  Misses        620      620              
  Partials      114      114              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@briansmith briansmith force-pushed the b/perf-is-not-like-silvermont branch from 95f66ef to 9e6a4e8 Compare February 4, 2025 20:07
This makes CPU feature detection simpler and helps the code coverage
testing effort.
@briansmith briansmith force-pushed the b/perf-is-not-like-silvermont branch from 9e6a4e8 to 4523def Compare February 4, 2025 20:12
@briansmith briansmith merged commit c10d400 into main Feb 4, 2025
172 checks passed
@briansmith briansmith deleted the b/perf-is-not-like-silvermont branch February 4, 2025 23:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant