From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Tony Camuso <tcamuso@redhat.com>
Cc: sam@ravnborg.org, linux-sparse@vger.kernel.org,
josh@joshtriplett.org, sparse@chrisli.org
Subject: Re: [PATCH 3/3 v4] Add Wall_off switch to disable errors and warnings
Date: Tue, 5 Jan 2016 02:19:59 +0100 [thread overview]
Message-ID: <20160105011958.GA12545@macpro.local> (raw)
In-Reply-To: <1438619759-14879-1-git-send-email-tcamuso@redhat.com>
On Mon, Aug 03, 2015 at 12:35:59PM -0400, Tony Camuso wrote:
> Disable all error reporting. Useful when semantic parsing checks are
> being done elsewhere or all you need is a tokenizer.
>
> Signed-off-by: Tony Camuso <tcamuso@redhat.com>
> ---
> lib.c | 27 +++++++++++++++++++++++----
> lib.h | 1 +
> 2 files changed, 24 insertions(+), 4 deletions(-)
>
> diff --git a/lib.c b/lib.c
> index 8dc5bcf..08f6a6b 100644
> --- a/lib.c
> +++ b/lib.c
...
> @@ -130,6 +135,12 @@ void info(struct position pos, const char * fmt, ...)
> static void do_error(struct position pos, const char * fmt, va_list args)
> {
> static int errors = 0;
> +
> + if (Wall_off) {
> + max_warnings = 0;
> + return;
> + }
> +
Is this really needed?
The same check in do_warn should be enough to quiet all messages, isn't it?
> @@ -479,6 +491,13 @@ static char **handle_onoff_switch(char *arg, char **next, const struct warning w
> char *p = arg + 1;
> unsigned i;
>
> + if (!strcmp(p, "all_off")) {
> + for (i = 0; i < n; i++)
> + *warnings[i].flag = WARNING_FORCE_OFF;
> + Wall_off = 1;
> + return NULL;
> + }
> +
Can't you simply set max_warnings to 0 already here
instead of doing it in do_warn()?
> @@ -127,6 +127,7 @@ extern int Wtypesign;
> extern int Wundef;
> extern int Wuninitialized;
> extern int Wvla;
> +extern int Wall_off;
I think it should be better to use a much more explicit name,
something like "ignore_all_warnings" for example.
Also it would be nice to document this new option in the man page.
Regards,
Luc
next prev parent reply other threads:[~2016-01-05 1:20 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 0:26 [PATCH 0/3] Minor enhancements and fixes Tony Camuso
2015-07-30 0:26 ` [PATCH 1/3] .gitignore: add cscope and Qt project files Tony Camuso
2015-08-03 17:41 ` [PATCH 1/3 v2] " Tony Camuso
2015-08-08 3:58 ` Christopher Li
2015-08-10 11:18 ` Tony Camuso
2015-08-10 12:33 ` [PATCH 1/3 v3] " Tony Camuso
2015-07-30 0:26 ` [PATCH 2/3] c2xml.c, parse.c: gcc 5+ stricter case statement parsing Tony Camuso
2015-08-04 12:06 ` [PATCH 2/3 v2] Handle all enum members in case statements Tony Camuso
2015-08-04 23:31 ` Christopher Li
2015-08-04 23:52 ` Tony Camuso
[not found] ` <CANeU7Q=QAtRqDP36k8uOd9_XgzqjJ0du5SO2WpMEcjp8+mg3CQ@mail.gmail.com>
2015-08-10 11:16 ` Tony Camuso
2015-08-10 12:35 ` [PATCH 2/3 v3] Add default case to switches on enum variables Tony Camuso
2015-07-30 0:26 ` [PATCH 3/3] Add NOWARN and NOERR compile conditions Tony Camuso
2015-07-30 2:55 ` Josh Triplett
2015-07-30 11:45 ` Tony Camuso
2015-07-31 23:46 ` Christopher Li
2015-08-01 11:09 ` Tony Camuso
2015-08-01 17:52 ` Josh Triplett
2015-08-01 18:45 ` Christopher Li
2015-08-02 13:42 ` Tony Camuso
2015-08-02 23:16 ` Tony Camuso
2015-08-02 23:22 ` Tony Camuso
2015-08-03 11:23 ` Nicolai Stange
2015-08-03 11:47 ` Tony Camuso
2015-07-31 17:07 ` Tony Camuso
2015-07-31 17:12 ` [PATCH 3/3 V2] lib.c: add Wall_off switch Tony Camuso
2015-07-31 18:01 ` Tony Camuso
2015-07-31 19:27 ` [PATCH 3/3 V3] Add Wall_off switch to disable errors and warnings Tony Camuso
2015-08-01 12:59 ` Sam Ravnborg
2015-08-01 13:52 ` Tony Camuso
2015-08-03 16:35 ` [PATCH 3/3 v4] " Tony Camuso
2016-01-05 1:19 ` Luc Van Oostenryck [this message]
2016-01-13 14:39 ` Tony Camuso
2015-08-03 18:10 ` [PATCH 0/3] Minor enhancements and fixes Tony Camuso
2015-12-02 18:52 ` Tony Camuso
2016-02-02 18:54 ` Christopher Li
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=20160105011958.GA12545@macpro.local \
--to=luc.vanoostenryck@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sparse@chrisli.org \
--cc=tcamuso@redhat.com \
/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 NNTP newsgroup(s).