All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-sparse@vger.kernel.org
Subject: Re: Feature request - allow boolean operations of undefined cpp symbols
Date: Fri, 02 Feb 2007 17:58:30 -0500	[thread overview]
Message-ID: <1170457110.4698.18.camel@dv> (raw)
In-Reply-To: <20070202221009.GC27667@chrisli.org>

On Fri, 2007-02-02 at 14:10 -0800, Christopher Li wrote:
> On Fri, Feb 02, 2007 at 05:30:37PM -0500, Pavel Roskin wrote:
> > 
> > You need -Wundef or -Wall to check for undefined preprocessor symbols.
> > 
> > $ sparse -Wundef test.c 
> > test.c:1:5: warning: undefined preprocessor identifier
> > 'SYMBOL_NOT_DEFINED'
> > test.c:4:2: warning: "not defined"
> 
> Ha, I see. So do you still want some thing more than -Wno-undef?

My intention was that we always allow boolean operations of undefined
cpp symbols, regardless of the flags.

Since Linus wants the existing strictness of -Wundef for the kernel, and
the kernel is sparse's "number one customer", I'll need to think of
something better to accommodate both the kernel and the userspace.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2007-02-02 22:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 17:37 Feature request - allow boolean operations of undefined cpp symbols Pavel Roskin
2007-02-02 18:25 ` Linus Torvalds
2007-02-02 21:56   ` Christopher Li
2007-02-02 22:30     ` Pavel Roskin
2007-02-02 22:10       ` Christopher Li
2007-02-02 22:58         ` Pavel Roskin [this message]
2007-02-02 22:45     ` Linus Torvalds
2007-04-20 10:02   ` Josh Triplett
2007-04-20 22:42     ` Pavel Roskin

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=1170457110.4698.18.camel@dv \
    --to=proski@gnu.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=sparse@chrisli.org \
    --cc=torvalds@linux-foundation.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.