linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Josh Triplett <josh@joshtriplett.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: Sparse preprocessing bug with zero-arg variadic macros
Date: Thu, 31 Aug 2017 20:06:12 -0400	[thread overview]
Message-ID: <CANeU7Q=CK7v0y3gmMzMOoduc2vV9bhPz_iCKQLFJXTPP54+t0g@mail.gmail.com> (raw)
In-Reply-To: <20170831214810.GS5426@ZenIV.linux.org.uk>

On Thu, Aug 31, 2017 at 5:48 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
>
> throw this in, perhaps?
>
> diff --git a/validation/preprocessor/preprocessor23.c b/validation/preprocessor/preprocessor23.c
> index 25be508..a778483 100644

This one does not have a signed off.
I will combine it with your previous patch.

I have test with your patch.
It fixes the simplified test example Linus give out.
I also do the stress test on allmodconfig kernel
source. There is no impact on sparse warning
given on kernel source. The stress test timing
is close enough.

I already apply the patch. I will push to master soon.

Thanks for the quick reply to fix this bug.

Chris

      reply	other threads:[~2017-09-01  0:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-31 13:34 Sparse preprocessing bug with zero-arg variadic macros Josh Poimboeuf
2017-08-31 17:19 ` Linus Torvalds
2017-08-31 20:54   ` Al Viro
2017-08-31 21:09     ` Al Viro
2017-08-31 21:34       ` Josh Triplett
2017-08-31 21:48         ` Al Viro
2017-09-01  0:06           ` Christopher Li [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='CANeU7Q=CK7v0y3gmMzMOoduc2vV9bhPz_iCKQLFJXTPP54+t0g@mail.gmail.com' \
    --to=sparse@chrisli.org \
    --cc=josh@joshtriplett.org \
    --cc=jpoimboe@redhat.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.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).