From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 2/4] fix prototype of __sync_bool_compare_and_swap()
Date: Tue, 6 Oct 2020 01:03:59 +0200 [thread overview]
Message-ID: <20201005230401.74777-3-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20201005230401.74777-1-luc.vanoostenryck@gmail.com>
The prototype was incomplete and typechecking failed after
some changes in the usual conversions.
So, add the full prototype.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
builtin.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin.c b/builtin.c
index 26b612dc401b..b134754b5831 100644
--- a/builtin.c
+++ b/builtin.c
@@ -607,7 +607,7 @@ static const struct builtin_fn builtins_common[] = {
{ "__sync_add_and_fetch", &int_ctype, 1, { &ptr_ctype }},
{ "__sync_and_and_fetch", &int_ctype, 1, { &ptr_ctype }},
- { "__sync_bool_compare_and_swap", &bool_ctype, 1, { &ptr_ctype }, .op = &sync_compare_and_swap_op},
+ { "__sync_bool_compare_and_swap", &bool_ctype, 1, { &bool_ptr_ctype, &bool_ctype, &bool_ctype }, .op = &sync_compare_and_swap_op},
{ "__sync_fetch_and_add", &int_ctype, 1, { &ptr_ctype }},
{ "__sync_fetch_and_and", &int_ctype, 1, { &ptr_ctype }},
{ "__sync_fetch_and_nand", &int_ctype, 1, { &ptr_ctype }},
--
2.28.0
next prev parent reply other threads:[~2020-10-05 23:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 23:03 [PATCH 0/4] fix usual conversion of integers Luc Van Oostenryck
2020-10-05 23:03 ` [PATCH 1/4] add builtin type pointer to bool: bool_ptr_ctype Luc Van Oostenryck
2020-10-05 23:03 ` Luc Van Oostenryck [this message]
2020-10-05 23:04 ` [PATCH 3/4] fix evaluation of pointer to bool conversions Luc Van Oostenryck
2020-10-05 23:04 ` [PATCH 4/4] fix usual conversion of integers Luc Van Oostenryck
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=20201005230401.74777-3-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.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).