Uh oh!
There was an error while loading. Please reload this page.
[fix](be) Fix unused constant/function build errors in md5.cpp - #63608
[fix](be) Fix unused constant/function build errors in md5.cpp #63608zwy991114 wants to merge 1 commit into
Conversation
zwy991114
commented
May 25, 2026
/review |
hello-stephen
commented
May 25, 2026
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
morrySnow
commented
Jun 1, 2026
run buildall |
morrySnow
commented
Jun 1, 2026
/review |
There was a problem hiding this comment.
Review result: no blocking issues found.
Critical checkpoint conclusions:
- Goal and tests: The PR aims to avoid unused constant/function build errors on non-AVX2 builds. The change accomplishes this by moving the AVX2-only constants and helpers under the same
__AVX2__guard as their only consumers. No new test is required for this mechanical build-guard adjustment. - Scope: The modification is small, clear, and focused on
be/src/util/md5.cpponly. - Concurrency: No concurrency behavior is involved.
- Lifecycle/static initialization: No non-trivial lifecycle or cross-translation-unit static initialization concern is introduced; the moved values are namespace-scope
constexprconstants and local helpers. - Configuration: No configuration item is added or changed.
- Compatibility: No function symbols, persisted data, wire protocol, or storage format are changed.
- Parallel paths: Both AVX2 and non-AVX2 paths still keep the shared
MD5_DUMMY_INPUTandmd5_to_hexcode available; AVX2-only helpers remain available only to the AVX2 path. - Conditional checks: The
__AVX2__guard matches the existing AVX2 implementation guard and is appropriate for these declarations. - Test coverage/results: Existing MD5 unit coverage remains applicable. No test result files are added or modified.
- Observability: Not applicable; no runtime behavior or diagnostics are changed.
- Transaction/persistence/data writes: Not applicable.
- FE/BE variable passing: Not applicable.
- Performance: No runtime performance impact expected.
- Other issues: None identified.
User focus points: No additional user-provided review focus was present.
Review notes: I attempted a local non-AVX2 syntax/warning check for be/src/util/md5.cpp, but the standalone command could not complete in this runner because required third-party headers were not available through that ad hoc include path. The code review conclusion is based on the PR diff and surrounding implementation.
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
hello-stephen
commented
Jun 1, 2026
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jun 1, 2026
TPC-H: Total hot run time: 28829 ms |
hello-stephen
commented
Jun 1, 2026
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jun 1, 2026
TPC-DS: Total hot run time: 170766 ms |
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #63484
Problem Summary:
The constants
MD5_A0/B0/C0/D0and the helper functionsmd5_num_blocks/md5_pad_final_blocksinbe/src/util/md5.cppare only referenced inside the#ifdef __AVX2__multi-buffer code path. On builds without AVX2 support, the compiler reports-Wunused-const-variableand-Wunused-function, which are promoted to errors via-Werrorand break the build.Move these AVX2-only declarations under the same
#ifdef __AVX2__guard that protects their sole consumer.MD5_DUMMY_INPUTandmd5_to_hexremain outside the guard since both code paths use them.Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)