This is an archive of the discontinued LLVM Phabricator instance.

[scudo] Enable more warnings for standalone build
ClosedPublic

Authored by ddcc on Mar 30 2022, 2:27 PM.

Diff Detail

Event Timeline

ddcc created this revision.Mar 30 2022, 2:27 PM
Herald added a project: Restricted Project. · View Herald TranscriptMar 30 2022, 2:27 PM
Herald added a subscriber: mgorny. · View Herald Transcript
ddcc requested review of this revision.Mar 30 2022, 2:27 PM
Herald added a project: Restricted Project. · View Herald TranscriptMar 30 2022, 2:27 PM
vitalybuka accepted this revision.Dec 7 2022, 1:29 PM
This revision is now accepted and ready to land.Dec 7 2022, 1:29 PM
This revision was automatically updated to reflect the committed changes.
lei added a subscriber: lei.EditedDec 12 2022, 7:26 AM

Please note that this patch broke any bots that build this project with -Werror (example: https://lab.llvm.org/buildbot/#/builders/19/builds/14037). As a result, I have reverted it since there has been no fix within a reasonable time.
May I advise ensuring that a project is clean wrt. to the additional warnings when turning on extra warnings as there are bound to be some builds that use -Werror. Also, new warnings are almost always disruptive changes as there are many different build configurations that may be affected in unforeseen ways. If you have such a disruptive change ready to commit, it is advisable to wait until Monday to commit it rather than committing it on a Friday evening as most people are disconnecting.

ddcc added a comment.Dec 12 2022, 11:20 AM

Sorry, I tested it when I opened the revision but forgot to account for changes since then.

vitalybuka reopened this revision.Dec 12 2022, 11:24 AM
This revision is now accepted and ready to land.Dec 12 2022, 11:24 AM
ddcc updated this revision to Diff 482324.Dec 12 2022, 5:37 PM

Add fix for unused variable

ddcc added a comment.Dec 12 2022, 5:38 PM

Ran a local build and this should be the only fix needed, will see what the CI results say