-
Notifications
You must be signed in to change notification settings - Fork 747
USe -WShadow in clang builds #12052
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
base: main
Are you sure you want to change the base?
USe -WShadow in clang builds #12052
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/12052
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 62 New FailuresAs of commit a4754da with merge base a2b620a ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
|
Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as |
Summary
Enable -Wshadow and -Werror=shadow for Clang builds. This is due to needing to revert or forward fix several commits when Meta-internal builds fail due to enforcing this. The option is enabled only on Clang as GCC's version is stricter (mainly around constructor parameters with the same name as class fields), which requires larger changes that I don't personally feel are necessary. Enforcing Clang's version in CI will be sufficient to prevent further reverts / issues as a result of shadowing.
Test plan
CI