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

fix requantize pack4to8 #5893

Merged
merged 6 commits into from
Feb 7, 2025
Merged

fix requantize pack4to8 #5893

merged 6 commits into from
Feb 7, 2025

Conversation

nihui
Copy link
Member

@nihui nihui commented Feb 5, 2025

No description provided.

@nihui nihui changed the title requantize pack4to1 and pack4to8 requantize pack4to8 Feb 5, 2025
@nihui nihui changed the title requantize pack4to8 fix requantize pack4to8 Feb 5, 2025
@codecov-commenter
Copy link

codecov-commenter commented Feb 5, 2025

Codecov Report

Attention: Patch coverage is 79.66102% with 24 lines in your changes missing coverage. Please review.

Project coverage is 94.59%. Comparing base (ff5b554) to head (b961c2e).
Report is 2 commits behind head on master.

Files with missing lines Patch % Lines
src/layer/x86/requantize_x86.cpp 76.23% 24 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           master    #5893       +/-   ##
===========================================
+ Coverage   92.08%   94.59%    +2.51%     
===========================================
  Files         293      648      +355     
  Lines       45647   219000   +173353     
===========================================
+ Hits        42032   207172   +165140     
- Misses       3615    11828     +8213     

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

@github-actions github-actions bot added the test label Feb 5, 2025
@nihui nihui merged commit 4a70be4 into Tencent:master Feb 7, 2025
66 of 80 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants