Skip to content

Use compiler-specific range-loop suppression flags - #2075

Closed
dajiaohuang wants to merge 2 commits into
AcademySoftwareFoundation:mainfrom
dajiaohuang:fix/gcc-range-loop-suppression
Closed

dajiaohuang wants to merge 2 commits into
AcademySoftwareFoundation:mainfrom
dajiaohuang:fix/gcc-range-loop-suppression

Conversation

@dajiaohuang

Copy link
Copy Markdown

Fixes #2036.

Use Clang's -Wno-range-loop-analysis only for Clang and AppleClang, and use GCC's -Wno-range-loop-construct for GNU compiler versions 11 and newer in both Python binding targets. The version guard preserves older documented VFX-platform compiler support, including GCC 9.3.1 for CY2022. Other warning suppressions and MSVC options are unchanged.

Validation:

  • Focused PowerShell static check for both targets passed.
  • git diff --check passed.
  • CMake configure/build and GCC/Clang verification were unavailable because CMake and C/C++ compilers are not installed in the environment; no tools or dependencies were installed.

@linux-foundation-easycla

linux-foundation-easycla Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: dajiaohuang / name: dajiaohuang (c53ec87)

@codecov-commenter

codecov-commenter commented Oct 21, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.61%. Comparing base (94e1ad6) to head (159e982).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2075   +/-   ##
=======================================
  Coverage   83.61%   83.61%           
=======================================
  Files         183      183           
  Lines       13580    13580           
  Branches     1261     1261           
=======================================
  Hits        11355    11355           
  Misses       2052     2052           
  Partials      173      173           
Flag Coverage Δ
py-unittests 83.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 94e1ad6...159e982. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@reinecke

Copy link
Copy Markdown
Collaborator

Hi @dajiaohuang - thanks for the contribution!

Would you mind doing the CLA authorization and making sure the contribution is commit with --signoff?

@dajiaohuang

Copy link
Copy Markdown
Author

Superseded by #2080, the same focused CMake patch on current main with the requested Signed-off-by trailer. #2080 is the replacement review location: #2080. No change to the original published commit/history.

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.

Clang warning suppression flag applied to gcc builds

3 participants