From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] Fix type checking of variadic functions
Date: Fri, 18 Nov 2016 13:30:06 +0100 [thread overview]
Message-ID: <20161118123005.GB476@macbook.local> (raw)
In-Reply-To: <CANeU7Qm0WbqFA1H6w7U=KmeLc90tyJdfsfQFqC4H_-c4mMQ1Hw@mail.gmail.com>
On Thu, Nov 17, 2016 at 08:06:41AM +0800, Christopher Li wrote:
> Speaking of the test case, there are two case can be added:
>
> void arg_incomplete();
> void arg_incomplete(int a) {} /* check-should-pass */
>
> void arg_incomplete_vararg();
> void arg_incomplete_vararg(int a, ...) {} /* check-should-fail */
>
> Sparse handle the first one incorrectly. But that is a separate issue,
> we can address it in a different patch.
>
> Will apply.
>
> Chris
> --
Yes. I'll look at this later.
Luc
prev parent reply other threads:[~2016-11-18 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 17:13 [PATCH] Fix type checking of variadic functions Luc Van Oostenryck
2016-11-17 0:06 ` Christopher Li
2016-11-18 12:30 ` Luc Van Oostenryck [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=20161118123005.GB476@macbook.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).