From: Dan Carpenter <dan.carpenter-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Sami Kerola <kerolasa-X3B1VOXEql0@public.gmane.org>
Cc: Karel Zak <kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
util-linux <util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-sparse-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/7] pull: make smatch scan output easy to digest
Date: Sat, 25 Feb 2017 23:09:13 +0300 [thread overview]
Message-ID: <20170225195901.GB4570@mwanda> (raw)
In-Reply-To: <alpine.LNX.2.20.1702251653080.16457@imuri>
On Sat, Feb 25, 2017 at 05:32:23PM +0000, Sami Kerola wrote:
> See below simple source file that demonstrates how to triggers warning in
> question. When I said was 'smatch' printed warnings it was cgcc that was
> complaining , and therefore this is not really a 'smatch' problem at all.
> Sorry about giving wrong impression.
cgcc is just a shell script which calls either smatch or sparse. Smatch
uses sparse as a parser so you sometimes do see certain sparse messages
when you run smatch, but I don't do bug fixes for those normally. You
would think I would understand sparse really well because I use it so
much but actually hacking sparse makes me realize I'm kind of dumb. ;P
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-02-25 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170213220641.1395-1-kerolasa@iki.fi>
[not found] ` <20170220121426.5mr6ab6x7pxt5j4b@ws.net.home>
[not found] ` <CAG27Bk2ENHD+1_sX0qVmVnKC2Ss7jDxSyqhNnaj6NKHNnitsYQ@mail.gmail.com>
[not found] ` <20170221095012.txqxcblrqkmoxktw@ws.net.home>
[not found] ` <20170223153049.GC4133@mwanda>
2017-02-25 17:32 ` [PATCH 0/7] pull: make smatch scan output easy to digest Sami Kerola
2017-02-25 20:09 ` Dan Carpenter [this message]
2017-02-26 4:07 ` Luc Van Oostenryck
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=20170225195901.GB4570@mwanda \
--to=dan.carpenter-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
--cc=kerolasa-X3B1VOXEql0@public.gmane.org \
--cc=kzak-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-sparse-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.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