From: josh@joshtriplett.org
To: Amit Sharma <amit.rinku.sharma072@gmail.com>
Cc: "linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Running Sparse twice on TOT produce the different set of warnings and error.!!
Date: Wed, 12 Nov 2014 11:06:21 -0800 [thread overview]
Message-ID: <20141112190621.GA21251@cloud> (raw)
In-Reply-To: <CAHK0xLu1rPGnCLZQDtjU1n_erjPJL9j-+WkZgpTPqvgc181e4w@mail.gmail.com>
On Wed, Nov 12, 2014 at 11:54:09PM +0530, Amit Sharma wrote:
> I just started to use the sparse and I was suppose to do some
> regression testing using sparse tool. What I observed during using of
> sparse is that it produces the different set of warnings and errors
> when we ran it twice on TOT without modifying anything in-between
> succession run of sparse. I just want to know is this is the known
> issue(Bug) of sparse ? If yes, can someone share here ?
Can you provide a sample of the differences?
How did you invoke Sparse? C=1 or C=2?
- Josh Triplett
prev parent reply other threads:[~2014-11-12 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 18:24 Running Sparse twice on TOT produce the different set of warnings and error.!! Amit Sharma
2014-11-12 19:06 ` josh [this message]
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=20141112190621.GA21251@cloud \
--to=josh@joshtriplett.org \
--cc=amit.rinku.sharma072@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-sparse@vger.kernel.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 NNTP newsgroup(s).