From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 3217F6A80 for ; Wed, 1 Jul 2015 13:10:34 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP; 01 Jul 2015 04:10:08 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,385,1432623600"; d="scan'208";a="756449061" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.162]) by orsmga002.jf.intel.com with SMTP; 01 Jul 2015 04:10:08 -0700 Received: by (sSMTP sendmail emulation); Wed, 01 Jul 2015 12:10:06 +0025 Date: Wed, 1 Jul 2015 12:10:06 +0100 From: Bruce Richardson To: Matthew Hall Message-ID: <20150701111005.GA2480@bricha3-MOBL3> References: <1A87AD2E-38CD-4C61-A9FD-C52608FF9DAC@mhcomputing.net> <39879033.dIVnPGkh8l@xps13> <386858255.20150629121137@intel.com> <2576181.dRfjlrHRWI@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] RTM instruction compile failure for XABORT when AVX is active X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2015 11:10:34 -0000 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 the issue using a setting there? /Bruce > 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 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 >