From: Josh Triplett <josh@freedesktop.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
Junio C Hamano <junkio@cox.net>,
GIT Mailing-list <git@vger.kernel.org>,
linux-sparse@vger.kernel.org
Subject: Re: [RFC][PATCH 00/10] Sparse: Git's "make check" target
Date: Sat, 09 Jun 2007 16:50:32 -0700 [thread overview]
Message-ID: <466B3CC8.4010508@freedesktop.org> (raw)
In-Reply-To: <20070609225630.GC3008@uranus.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
Sam Ravnborg wrote:
>> Also, you might consider just using cgcc to run both GCC and Sparse. That
>> would handle the issue of target-specific CFLAGS, by ensuring that Sparse and
>> GCC always see the same CFLAGS.
>
> Is this the recommended way?
> I that case I suggest that someone looks into the linux kernel part
> and change it to use this method.
The approach taken by Linux allows running sparse on files without recompiling
them. Using CC=cgcc just makes for less work, but the kernel has that work
done now.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-06-09 23:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 22:06 [RFC][PATCH 00/10] Sparse: Git's "make check" target Ramsay Jones
2007-06-09 7:08 ` Josh Triplett
2007-06-09 22:56 ` Sam Ravnborg
2007-06-09 23:50 ` Josh Triplett [this message]
2007-06-12 17:37 ` Ramsay Jones
2007-06-13 20:25 ` 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=466B3CC8.4010508@freedesktop.org \
--to=josh@freedesktop.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
--cc=sam@ravnborg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.