From: Johannes Berg <johannes@sipsolutions.net>
To: Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Nicolai Stange <nicstange@gmail.com>
Subject: Re: [PATCH v2] implement constant-folding in __builtin_bswap*()
Date: Wed, 23 Nov 2016 07:28:27 +0100 [thread overview]
Message-ID: <1479882507.4432.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CANeU7QmSd5Zd_H2jDQyTjUMg7C4_6wQOyCR73R=FTdJ=f4+ygg@mail.gmail.com> (sfid-20161122_174738_216238_D863CDDD)
> I get it working in the end. Not too far from what I thought.
> Patch attach here for review.
Just a small comment:
> + if (expression_list_size(args) != 1) {
> + sparse_error(expr->pos, "not enough arguments for function %s",
> + show_ident(sym->ident));
Should that say "invalid number of arguments (expected 1)" or so?
johannes
next prev parent reply other threads:[~2016-11-23 6:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 9:55 [PATCH v2] implement constant-folding in __builtin_bswap*() Johannes Berg
2016-11-21 2:38 ` Christopher Li
2016-11-21 9:45 ` Johannes Berg
2016-11-22 11:13 ` Christopher Li
2016-11-22 11:39 ` Christopher Li
2016-11-22 13:15 ` Luc Van Oostenryck
2016-11-22 16:32 ` Christopher Li
2016-11-22 17:12 ` Luc Van Oostenryck
2016-11-23 1:23 ` Christopher Li
2016-11-22 20:16 ` Luc Van Oostenryck
2016-11-23 1:25 ` Christopher Li
2016-11-23 20:38 ` [PATCH] add test case for builtin bswap with constant args Luc Van Oostenryck
2016-11-24 0:17 ` Christopher Li
2016-11-24 5:30 ` Christopher Li
2016-11-24 13:00 ` Luc Van Oostenryck
2016-11-23 20:48 ` [PATCH v2] implement constant-folding in __builtin_bswap*() Luc Van Oostenryck
2016-11-24 0:56 ` Christopher Li
2016-11-24 0:58 ` Christopher Li
2016-11-24 1:36 ` Luc Van Oostenryck
2016-11-24 3:17 ` Christopher Li
2016-11-24 1:31 ` Luc Van Oostenryck
2016-11-24 3:23 ` Christopher Li
2016-11-23 6:28 ` Johannes Berg [this message]
2016-11-23 14:30 ` 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=1479882507.4432.1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=nicstange@gmail.com \
--cc=sparse@chrisli.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).