https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106572
--- Comment #4 from Jayesh Badwaik <j.badw...@fz-juelich.de> --- I don't think any of the previous bug reports address the requirements that this bug report does. This is not about production runs, this is about development workflow. Unless the position is that users should not use any warnings apart from `-Wall -Wextra` ever, the user has to look at what warnings the compiler offers. The current method is a very manual method where I have to browse through the whole GCC page and get the list of warnings and then manually put them into my command line to see if any of the code in my repository triggers those warnings. It will save everyone's time and effort if there was a switch to do that. It is therefore, actually very useful.
