DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] common/rte_memcpy: Fix x86intrin.h missed
Date: Mon, 16 Mar 2015 17:39:31 +0000	[thread overview]
Message-ID: <2601191342CEEE43887BDE71AB977258213F6BEB@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <6230385.qXqGPvIMiq@xps13>

Hi Thomas,

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Monday, March 16, 2015 4:05 PM
> To: Ananyev, Konstantin
> Cc: dev@dpdk.org; Qiu, Michael
> Subject: Re: [dpdk-dev] [PATCH] common/rte_memcpy: Fix x86intrin.h missed
> 
> 2015-03-13 09:44, Ananyev, Konstantin:
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Michael Qiu
> > >
> > > rte_memcpy.h(46): catastrophic error: cannot open source file "x86intrin.h"
> > >
> > > For icc and old gcc, this header is not included.
> > >
> > > Signed-off-by: Michael Qiu <michael.qiu@intel.com>
> > > ---
> > >  lib/librte_eal/common/include/arch/x86/rte_memcpy.h | 20 ++++++++++++++++++++
> > >  1 file changed, 20 insertions(+)
> > >
> > > diff --git a/lib/librte_eal/common/include/arch/x86/rte_memcpy.h b/lib/librte_eal/common/include/arch/x86/rte_memcpy.h
> > > index ac72069..bd10d36 100644
> > > --- a/lib/librte_eal/common/include/arch/x86/rte_memcpy.h
> > > +++ b/lib/librte_eal/common/include/arch/x86/rte_memcpy.h
> > > @@ -43,7 +43,27 @@
> > >  #include <stdio.h>
> > >  #include <stdint.h>
> > >  #include <string.h>
> > > +#if (defined(__ICC) || (__GNUC__ == 4 &&  __GNUC_MINOR__ < 4))
> > > +
> > > +#ifdef __SSE__
> > > +#include <xmmintrin.h>
> > > +#endif
> > > +
> > > +#ifdef __SSE2__
> > > +#include <emmintrin.h>
> > > +#endif
> > > +
> > > +#if defined(__SSE4_2__) || defined(__SSE4_1__)
> > > +#include <smmintrin.h>
> > > +#endif
> > > +
> > > +#if defined(__AVX__)
> > > +#include <immintrin.h>
> > > +#endif
> > > +
> > > +#else
> > >  #include <x86intrin.h>
> > > +#endif
> > >
> > >  #ifdef __cplusplus
> > >  extern "C" {
> > > --
> > > 1.9.3
> >
> > Wonder why to spread this thing over?
> > Why not just #include <rte_common_vec.h>?
> 
> I agree to use rte_common_vec.h.
> I pushed this approach to check every tested compilers:
> 	http://dpdk.org/browse/dpdk/commit/?id=9a01c31b94e54384
> 
> I think that rte_common_vec.h should be moved into
> lib/librte_eal/common/include/arch/x86/rte_vec.h as it's x86-specific.

Seems like a good thing to do.
Do you want me to submit a patch for 2.0 for that?

Konstantin

  reply	other threads:[~2015-03-16 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  7:02 Michael Qiu
2015-03-13  7:08 ` Wang, Zhihong
2015-03-13  9:44 ` Ananyev, Konstantin
2015-03-16 16:05   ` Thomas Monjalon
2015-03-16 17:39     ` Ananyev, Konstantin [this message]
2015-03-17  8:46       ` Thomas Monjalon
2015-03-18  4:48   ` Qiu, Michael
2015-03-13 14:25 ` Mcnamara, John
2015-03-16  4:44   ` Qiu, Michael

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=2601191342CEEE43887BDE71AB977258213F6BEB@irsmsx105.ger.corp.intel.com \
    --to=konstantin.ananyev@intel.com \
    --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).