{"push_id":974185728,"size":1,"distinct_size":1,"ref":"refs/heads/96971-clean-benign-release-build-warnings","head":"9cedb406bb8930c17cfd559423f1a5873a3326f4","before":"fcd8d9a7bbd7f8dbf52555e4430dc5bf7e87bd1a","commits":[{"sha":"9cedb406bb8930c17cfd559423f1a5873a3326f4","author":{"email":"96f164ad4d9b2b0dacf8ebee2bb1eeb3aa69adf1@ericfontainejazz.com","name":"Eric Fontaine"},"message":"fix #96971 suppress benign make release warnings\n\nThis commit removes some -Wempty-body, -Wmaybe-uninitialized, -Wunused-variable, and -Wstrict-overflow compiler warnings that arise on my x86-64 and ARM arch linux machines when compiling release.\nThese compiler warnings don't seem to cause any bugs, but since they pollute the build output, they make it harder to spot potentially important warnings that might arise, so I'm making these small changes to keep the build output clean.\nThe \"empty-body\" warnings occur because the Q_ASSERT statements are removed for release compiles, causing the else blocks to be empty.  Surrounding the Q_ASSERT with brackets will let the compiler know we aren't unintentionally having an empty else body.\nThe \"maybe-uninitialized\" warnings are handled by assigning the variables to 0 either at initialization or in a switch default block.\nThe \"unused-variable\" warning is due to PeriodItem updatePeriods[] in preferences.cpp being defined but never used, so I've removed PeriodItem.","distinct":true,"url":"https://api.github.com/repos/ericfont/MuseScore/commits/9cedb406bb8930c17cfd559423f1a5873a3326f4"}]}