From: Randy Dunlap <rdunlap@xenotime.net>
To: linux-sparse@vger.kernel.org
Subject: barrier macro
Date: Tue, 1 May 2007 15:34:48 -0700 [thread overview]
Message-ID: <20070501153448.a65c81c2.rdunlap@xenotime.net> (raw)
(using sparse 0.3)
./compiler-gcc.h:10:#define barrier() __asm__ __volatile__("": : :"memory")
causes this output:
net/sunrpc/xprtsock.c:640:2: error: Expected ( after asm
net/sunrpc/xprtsock.c:640:2: error: got __volatile__
net/sunrpc/xprtsock.c:640:2: error: typename in expression
net/sunrpc/xprtsock.c:640:2: error: Expected ) in function call
net/sunrpc/xprtsock.c:640:2: error: got :
Maybe sparse could allow modifiers between asm|__asm__ and the
(...) ?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next reply other threads:[~2007-05-01 22:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 22:34 Randy Dunlap [this message]
2007-05-02 3:17 ` barrier macro Josh Triplett
2007-05-02 4:04 ` Randy Dunlap
2007-05-02 4:11 ` Josh Triplett
2007-05-02 4:24 ` Josh Triplett
2007-05-02 4:35 ` Randy Dunlap
2007-05-02 5:37 ` Josh Triplett
2007-05-02 7:20 ` Christopher Li
2007-05-02 18:11 ` Josh Triplett
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=20070501153448.a65c81c2.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--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).