[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-07-01 Thread Bruce Richardson
On Tue, Jun 30, 2015 at 10:49:26PM -0700, Matthew Hall wrote: > With those two items commented out, and these CFLAGS: > > "-g -O0 -fPIC -msse4.2" > The recommended way of specifying a particular instruction set is via the RTE_MACHINE setting in your build time config. Can you perhaps reproduce

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-07-01 Thread Matthew Hall
Previously, with the -msse4.2 flag removed, the build failed for a different reason. I can retry without it and see if it's the case in the new DPDK. On Jul 1, 2015, at 4:10 AM, Bruce Richardson wrote: > On Tue, Jun 30, 2015 at 10:49:26PM -0700, Matthew Hall wrote: >> With those two items

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-06-30 Thread Matthew Hall
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" ::

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-06-30 Thread Matthew Hall
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

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-06-30 Thread Matthew Hall
On Jun 29, 2015, at 3:19 AM, Thomas Monjalon wrote: > There is no such bug with my compiler: > clang version 3.6.1 (tags/RELEASE_361/final) > Target: x86_64-unknown-linux-gnu > > Matthew, which version are you using? Hi Thomas and Roman, It seems to happen if I have set -mavx in

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-06-29 Thread Thomas Monjalon
2015-06-29 12:11, Roman Dementiev: > >> On Jun 28, 2015, at 10:16 AM, Matthew Hall > >> wrote: > >> > 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

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-06-29 Thread Roman Dementiev
Hello Thomas, Sunday, June 28, 2015, 9:38:14 PM, you wrote: > 2015-06-28 10:59, Matthew Hall: >> It would appear there is some bug in the new lock elision patches that is >> preventing it from compiling with clang. Any suggestions? > It builds with clang. > My suggestion is to add the patch

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-06-28 Thread Thomas Monjalon
2015-06-28 10:59, Matthew Hall: > It would appear there is some bug in the new lock elision patches that is > preventing it from compiling with clang. Any suggestions? It builds with clang. My suggestion is to add the patch author in recipient's list ;) > On Jun 28, 2015, at 10:16 AM, Matthew

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-06-28 Thread Matthew Hall
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 wrote: > Hi all, > > I am getting a strange error compiling some RTM instructions when I upgraded > my VM environment

[dpdk-dev] RTM instruction compile failure for XABORT when AVX is active

2015-06-28 Thread Matthew Hall
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