From: Matthew Hall <mhall@mhcomputing.net>
To: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] RTM instruction compile failure for XABORT when AVX is active
Date: Sun, 28 Jun 2015 10:59:53 -0700 [thread overview]
Message-ID: <038E8439-A99C-40BB-9A77-B20024E4111F@mhcomputing.net> (raw)
In-Reply-To: <1A87AD2E-38CD-4C61-A9FD-C52608FF9DAC@mhcomputing.net>
It would appear there is some bug in the new lock elision patches that is preventing it from compiling with clang. Any suggestions?
On Jun 28, 2015, at 10:16 AM, Matthew Hall <mhall@mhcomputing.net> wrote:
> Hi all,
>
> I am getting a strange error compiling some RTM instructions when I upgraded my VM environment from VirtualBox 4 to VirtualBox 5 and AVX instructions from the host CPU became available. However when I am reading the opcode description for XABORT it supposedly allows an immediate operand for the argument so I can't understand why this code would not compile. Any advice?
>
> CC test_hash_scaling.o
> In file included from /vagrant/external/dpdk/app/test/test_hash_scaling.c:37:
> In file included from /vagrant/external/dpdk/build/include/rte_spinlock.h:42:
> /vagrant/external/dpdk/build/include/rte_rtm.h:56:15: error: invalid operand for inline asm constraint 'i'
> asm volatile(".byte 0xc6,0xf8,%P0" :: "i" (status) : "memory");
>
> Matthew.
next prev parent reply other threads:[~2015-06-28 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 17:16 Matthew Hall
2015-06-28 17:59 ` Matthew Hall [this message]
2015-06-28 19:38 ` Thomas Monjalon
2015-06-29 10:11 ` Roman Dementiev
2015-06-29 10:19 ` Thomas Monjalon
2015-07-01 4:28 ` Matthew Hall
2015-07-01 5:17 ` Matthew Hall
2015-07-01 5:49 ` Matthew Hall
2015-07-01 11:10 ` Bruce Richardson
2015-07-01 15:53 ` Matthew Hall
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=038E8439-A99C-40BB-9A77-B20024E4111F@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.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).