From: "Alexander Shishkin" <alexander.shishckin@gmail.com>
To: Bernd Petrovitsch <bernd@firmix.at>
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 12:19:07 +0300 [thread overview]
Message-ID: <71a0d6ff0808260219k25771d4yf5ca6deceea60fbe@mail.gmail.com> (raw)
In-Reply-To: <1219736666.21663.12.camel@spike.firmix.at>
On Tue, Aug 26, 2008 at 10:44 AM, Bernd Petrovitsch <bernd@firmix.at> wrote:
> I (obviously) don't know any details about your situation but do you
> have any specific reason that you have different sets of -I/-D
> parameters on dependency generation and the real compile run?
To put a long story short: I run sparse against netbsd tree. To be
slightly more elaborate, I should mention that I wasn't able so far to
fully appreciate the beauty and elegance of certain design decisions
of the project in question. Nevertheless, I'm seeing different reports
from gendep and compilation runs.
> Personally I see only subtle problems on the horizon with such a
> situation.
> Let alone that it is somewhat simpler to have *one* CFLAGS/CPPFLAGS/...
> variable and use that everywhere.
Well, that aside, the overall build time significantly increases with
having to run sparse twice. Same warnings/errors are reported twice.
I still think that sparse has no business validating any code when
cgcc is called in -M mode; all those files are going to be compiled
later on anyway. And it's the compilation stage where warnings are
desirable.
Regards,
--
Alex
next prev parent reply other threads:[~2008-08-26 9:19 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 [this message]
2008-08-26 10:00 ` Bernd Petrovitsch
2008-08-27 0:43 ` Josh Triplett
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=71a0d6ff0808260219k25771d4yf5ca6deceea60fbe@mail.gmail.com \
--to=alexander.shishckin@gmail.com \
--cc=bernd@firmix.at \
--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).