From: Pavel Roskin <proski@gnu.org>
To: Pierre Habouzit <madcoder@debian.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: feature-request
Date: Mon, 25 Feb 2008 09:22:49 -0500 [thread overview]
Message-ID: <1203949369.802.22.camel@dv> (raw)
In-Reply-To: <20080225085408.GA9390@artemis.madism.org>
On Mon, 2008-02-25 at 09:54 +0100, Pierre Habouzit wrote:
> > Perhaps a simpler approach would be to turn off warnings in any files
> > included using angle brackets.
>
> Nope, that's not good, because I use angle brackets to #include files
> from my projects when I use internally in-tree headers that will in the
> end be public.
>
> I'd rather like to ask to ignore warnings for example, for file under
> /usr/include and /usr/lib/gcc/
You are right. I think sparse should try to follow gcc in this regard.
There are three hardcoded directories in pre-process.c
(/usr/include, /usr/local/include and the gcc include directory). Maybe
they should be considered system include directories.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2008-02-25 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 13:39 feature-request Pierre Habouzit
2008-02-25 2:48 ` feature-request Pavel Roskin
2008-02-25 8:54 ` feature-request Pierre Habouzit
2008-02-25 14:22 ` Pavel Roskin [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=1203949369.802.22.camel@dv \
--to=proski@gnu.org \
--cc=linux-sparse@vger.kernel.org \
--cc=madcoder@debian.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).