From: Matthew Hall <mhall@mhcomputing.net>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] RTM instruction compile failure for XABORT when AVX is active
Date: Tue, 30 Jun 2015 22:49:26 -0700 [thread overview]
Message-ID: <E58B86F0-1853-4A30-AF1E-6FEF78CAEC48@mhcomputing.net> (raw)
In-Reply-To: <C0759555-9A77-4AE2-B00F-79C123C0606C@mhcomputing.net>
With those two items commented out, and these CFLAGS:
"-g -O0 -fPIC -msse4.2"
it looks like I can reproduce the issue in clang 2.6 series:
/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");
So there are definitely some corner cases that seem to be able to trigger it.
On Jun 30, 2015, at 10:17 PM, Matthew Hall <mhall@mhcomputing.net> wrote:
> To be a bit more specific, this is what I had to do to fix it for clang 3.6 SVN snapshot release.
>
> I am not sure if there is a better way of handling this situation. I'd love to know where I could improve it.
>
> Matthew.
>
> diff --git a/mk/rte.cpuflags.mk b/mk/rte.cpuflags.mk
> index f595cd0..8c883ee 100644
> --- a/mk/rte.cpuflags.mk
> +++ b/mk/rte.cpuflags.mk
> @@ -77,13 +77,13 @@ ifneq ($(filter $(AUTO_CPUFLAGS),__RDRND__),)
> CPUFLAGS += RDRAND
> endif
>
> -ifneq ($(filter $(AUTO_CPUFLAGS),__FSGSBASE__),)
> -CPUFLAGS += FSGSBASE
> -endif
> +#ifneq ($(filter $(AUTO_CPUFLAGS),__FSGSBASE__),)
> +#CPUFLAGS += FSGSBASE
> +#endif
>
> -ifneq ($(filter $(AUTO_CPUFLAGS),__F16C__),)
> -CPUFLAGS += F16C
> -endif
> +#ifneq ($(filter $(AUTO_CPUFLAGS),__F16C__),)
> +#CPUFLAGS += F16C
> +#endif
>
> ifneq ($(filter $(AUTO_CPUFLAGS),__AVX2__),)
> CPUFLAGS += AVX2
next prev parent reply other threads:[~2015-07-01 5:49 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
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 [this message]
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=E58B86F0-1853-4A30-AF1E-6FEF78CAEC48@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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).