# HG changeset patch # User Miko Mynttinen # Date 1527854970 -7200 # Node ID f02640343be7b12a1a18cc9fd688056b93b4c2fe # Parent a0d11b55d5957a488b41420c4f6cc178df7cd2e7 Bug 1465060 - Part 2: Don't suppress pessimizing-move and self-move warnings r=froydnj MozReview-Commit-ID: KtQ31q6uFqZ diff --git a/build/moz.configure/warnings.configure b/build/moz.configure/warnings.configure --- a/build/moz.configure/warnings.configure +++ b/build/moz.configure/warnings.configure @@ -81,22 +81,16 @@ check_and_add_gcc_warning('-Wstring-conv # we inline 'new' and 'delete' in mozalloc check_and_add_gcc_warning('-Wno-inline-new-delete', cxx_compiler) # Prevent the following GCC warnings from being treated as errors: # too many false positives check_and_add_gcc_warning('-Wno-error=maybe-uninitialized') -# Turned on by -Wall, but needs changes to be turned into an error -# (bug 1465060). -check_and_add_gcc_warning('-Wno-error=pessimizing-move') -# This one is probably easier, it's only triggered by tests. -check_and_add_gcc_warning('-Wno-error=self-move') - # we don't want our builds held hostage when a platform-specific API # becomes deprecated. check_and_add_gcc_warning('-Wno-error=deprecated-declarations') # false positives depending on optimization check_and_add_gcc_warning('-Wno-error=array-bounds') # can't get rid of those PGO warnings