DPDK patches and discussions
 help / color / mirror / Atom feed
From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] examples: fix build errors for icc
Date: Mon, 4 Apr 2016 09:33:39 +0000	[thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8E46B6@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1459759611-13788-3-git-send-email-danielx.t.mrzyglod@intel.com>

Hi Daniel,

> -----Original Message-----
> From: Mrzyglod, DanielX T
> Sent: Monday, April 04, 2016 9:47 AM
> To: dev@dpdk.org
> Cc: Wu, Jingjing; De Lara Guarch, Pablo
> Subject: [PATCH 2/2] examples: fix build errors for icc
> 
> error: loops in this subroutine are not good vectorization candidates
>  (try compiling with O3 and/or IPO).
> 
> Solution to disable this diagnostic message
> https://software.intel.com/en-us/forums/intel-c-compiler/topic/537688
> 
> Fixes: d299106e8e31 ("examples/ipsec-secgw: add IPsec sample application")
> Fixes: 8cc72f2814dd ("examples/vmdq_dcb: support X710")
> 
> Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
 
Which ICC version are you using? I don't see any errors with ICC 15.0, so is it with 16.0?

Thanks,
Pablo

  reply	other threads:[~2016-04-04  9:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-04  8:46 [dpdk-dev] [PATCH 0/2] fixes for icc build errors Daniel Mrzyglod
2016-04-04  8:46 ` [dpdk-dev] [PATCH 1/2] examples/l2fwd-crypto: fix for icc Daniel Mrzyglod
2016-04-04  9:34   ` De Lara Guarch, Pablo
2016-04-04  8:46 ` [dpdk-dev] [PATCH 2/2] examples: fix build errors " Daniel Mrzyglod
2016-04-04  9:33   ` De Lara Guarch, Pablo [this message]
2016-04-04  9:38     ` Mrzyglod, DanielX T
2016-04-04 10:26       ` De Lara Guarch, Pablo
2016-04-04 10:56   ` [dpdk-dev] [PATCH v2] " Daniel Mrzyglod
2016-04-04 13:07 ` [dpdk-dev] [PATCH 0/2] fixes for icc build errors Thomas Monjalon

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=E115CCD9D858EF4F90C690B0DCB4D8973C8E46B6@IRSMSX108.ger.corp.intel.com \
    --to=pablo.de.lara.guarch@intel.com \
    --cc=danielx.t.mrzyglod@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.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).