From: Josh Triplett <josht@linux.vnet.ibm.com>
To: Alexander Shishkin <alexander.shishckin@gmail.com>
Cc: sparse development list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] don't call sparse when called to generate dependencies
Date: Tue, 26 Aug 2008 17:43:04 -0700 [thread overview]
Message-ID: <1219797784.6911.9.camel@josh-work.beaverton.ibm.com> (raw)
In-Reply-To: <1219700019-19627-1-git-send-email-alexander.shishckin@gmail.com>
On Tue, 2008-08-26 at 00:33 +0300, Alexander Shishkin wrote:
> I have a situation here when $(CC) is called with -M options with
> slighly different set of -I/-D/etc arguments, which causes all sorts of
> funny reports from sparse. Also, this increases the overall build time
> because every compilation unit if sparsed twice.
Makes sense, given that -M implies -E. Applied, thanks.
- Josh Triplett
prev parent reply other threads:[~2008-08-27 0:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-25 21:33 [PATCH] don't call sparse when called to generate dependencies Alexander Shishkin
2008-08-26 7:44 ` Bernd Petrovitsch
2008-08-26 9:19 ` Alexander Shishkin
2008-08-26 10:00 ` Bernd Petrovitsch
2008-08-27 0:43 ` Josh Triplett [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=1219797784.6911.9.camel@josh-work.beaverton.ibm.com \
--to=josht@linux.vnet.ibm.com \
--cc=alexander.shishckin@gmail.com \
--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).