From: Christopher Li <sparse@chrisli.org>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 5/5] lib.c: Add __sync_lock_test_and_set as a builtin function
Date: Wed, 22 May 2013 20:15:44 -0700 [thread overview]
Message-ID: <CANeU7Qkv7UkmFnQ__6q5zRkM8CTAUhwWhronFh-c70GLz-Q7QA@mail.gmail.com> (raw)
In-Reply-To: <519BC8AF.8060804@ramsay1.demon.co.uk>
On Tue, May 21, 2013 at 12:19 PM, Ramsay Jones
<ramsay@ramsay1.demon.co.uk> wrote:
> + add_pre_buffer("extern int __sync_lock_test_and_set(volatile long *const, const long);\n");
Looking at the gcc documents about atomic builtins. quote:
"and further that they are overloaded such that they work on multiple types"
Sparse does not do type overload. Which means sparse can't properly support this
function right now. If some one try to use this function on an int
type, sparse will
complain about type mismatch.
Chris
next prev parent reply other threads:[~2013-05-23 3:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 19:19 [PATCH 5/5] lib.c: Add __sync_lock_test_and_set as a builtin function Ramsay Jones
2013-05-23 3:15 ` Christopher Li [this message]
2013-05-25 19:40 ` Ramsay Jones
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=CANeU7Qkv7UkmFnQ__6q5zRkM8CTAUhwWhronFh-c70GLz-Q7QA@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.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).