public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "j.badwaik@fz-juelich.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/106572] A programmatic list of all possible compiler warnings
Date: Tue, 09 Aug 2022 14:53:25 +0000	[thread overview]
Message-ID: <bug-106572-4-CI64XtcokQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106572-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106572

--- Comment #4 from Jayesh Badwaik <j.badwaik@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.

  parent reply	other threads:[~2022-08-09 14:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 14:40 [Bug c++/106572] New: " j.badwaik@fz-juelich.de
2022-08-09 14:43 ` [Bug c++/106572] " mpolacek at gcc dot gnu.org
2022-08-09 14:43 ` pinskia at gcc dot gnu.org
2022-08-09 14:51 ` j.badwaik@fz-juelich.de
2022-08-09 14:53 ` j.badwaik@fz-juelich.de [this message]
2022-08-09 15:10 ` pinskia at gcc dot gnu.org
2022-08-09 15:14 ` pinskia at gcc dot gnu.org
2022-08-10  7:02 ` rguenth at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-106572-4-CI64XtcokQ@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).