From: Avi Kivity <avi@redhat.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-sparse@vger.kernel.org
Subject: Re: vector_size attribute?
Date: Sun, 29 May 2011 19:26:24 +0300 [thread overview]
Message-ID: <4DE273B0.7000800@redhat.com> (raw)
In-Reply-To: <20110529085726.c0234647.rdunlap@xenotime.net>
On 05/29/2011 06:57 PM, Randy Dunlap wrote:
> Current Linux mainline generates a ton of sparse warnings like
>
> arch/x86/include/asm/kvm_emulate.h:194:28: error: attribute 'vector_size': unknown attribute
>
> from this source line:
>
> typedef u32 __attribute__((vector_size(16))) sse128_t;
I guess sparse should be taught about it. It's needed so that gcc asm
constraints are aware of what memory is touched when running an sse
instruction.
(probably ignoring it for now should be sufficient)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-29 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 15:57 vector_size attribute? Randy Dunlap
2011-05-29 16:26 ` Avi Kivity [this message]
2011-05-31 11:22 ` Christopher Li
2011-05-31 18:31 ` Randy Dunlap
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=4DE273B0.7000800@redhat.com \
--to=avi@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).