From: Josh Triplett <josh@freedesktop.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Christopher Li <sparse@chrisli.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] allow ifdef in macro arguments
Date: Sun, 21 Oct 2007 17:03:52 -0700 [thread overview]
Message-ID: <471BE8E8.3020200@freedesktop.org> (raw)
In-Reply-To: <20071021155211.GX8181@ftp.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 640 bytes --]
Al Viro wrote:
> On Sun, Oct 21, 2007 at 02:07:15AM -0700, Christopher Li wrote:
>> I think some one report it long time ago.
>
> It should not accept those. Undefined behaviour and if you try to actually
> define the semantics for it, you run into such a pile of corner cases that
> it's not worth even trying.
Do you think the cases handled by GCC warrant making an attempt and
warning about it, or should Sparse just throw up its hands and give
up?
If the latter, should Sparse make any attempt at all to detect
preprocessor conditionals in macro arguments so it can give a more
specific warning?
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-10-22 0:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 9:07 [PATCH] allow ifdef in macro arguments Christopher Li
2007-10-21 9:18 ` Ralf Wildenhues
2007-10-21 15:52 ` Al Viro
2007-10-22 0:03 ` Josh Triplett [this message]
2007-10-22 16:13 ` Christopher Li
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=471BE8E8.3020200@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=viro@ftp.linux.org.uk \
/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).