From: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
To: dev@dpdk.org
Cc: jingjing.wu@intel.com, pablo.de.lara.guarch@intel.com
Subject: [PATCH v2] examples: fix build errors for icc
Date: Mon, 4 Apr 2016 12:56:54 +0200 [thread overview]
Message-ID: <1459767414-8416-1-git-send-email-danielx.t.mrzyglod@intel.com> (raw)
In-Reply-To: <1459759611-13788-3-git-send-email-danielx.t.mrzyglod@intel.com>
error: loops in this subroutine are not good vectorization candidates
(try compiling with O3 and/or IPO).
this error occurs in icc 15.0.1
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>
---
examples/ipsec-secgw/Makefile | 4 ++++
examples/vmdq_dcb/Makefile | 4 +++-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/examples/ipsec-secgw/Makefile b/examples/ipsec-secgw/Makefile
index da39e49..f9b59c2 100644
--- a/examples/ipsec-secgw/Makefile
+++ b/examples/ipsec-secgw/Makefile
@@ -42,6 +42,10 @@ APP = ipsec-secgw
CFLAGS += -O3 -gdwarf-2
CFLAGS += $(WERROR_FLAGS)
+ifeq ($(CONFIG_RTE_TOOLCHAIN_ICC),y)
+CFLAGS_sa.o += -diag-disable=vec
+endif
+
VPATH += $(SRCDIR)/librte_ipsec
diff --git a/examples/vmdq_dcb/Makefile b/examples/vmdq_dcb/Makefile
index 10a9a9a..8c51131 100644
--- a/examples/vmdq_dcb/Makefile
+++ b/examples/vmdq_dcb/Makefile
@@ -51,7 +51,9 @@ CFLAGS += $(WERROR_FLAGS)
ifeq ($(CONFIG_RTE_TOOLCHAIN_GCC),y)
CFLAGS_main.o += -Wno-return-type
endif
-
+ifeq ($(CONFIG_RTE_TOOLCHAIN_ICC),y)
+CFLAGS_main.o += -diag-disable=vec
+endif
EXTRA_CFLAGS += -O3 -g
include $(RTE_SDK)/mk/rte.extapp.mk
--
2.5.5
next prev parent reply other threads:[~2016-04-04 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 8:46 [PATCH 0/2] fixes for icc build errors Daniel Mrzyglod
2016-04-04 8:46 ` [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 ` [PATCH 2/2] examples: fix build errors " Daniel Mrzyglod
2016-04-04 9:33 ` De Lara Guarch, Pablo
2016-04-04 9:38 ` Mrzyglod, DanielX T
2016-04-04 10:26 ` De Lara Guarch, Pablo
2016-04-04 10:56 ` Daniel Mrzyglod [this message]
2016-04-04 13:07 ` [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=1459767414-8416-1-git-send-email-danielx.t.mrzyglod@intel.com \
--to=danielx.t.mrzyglod@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=pablo.de.lara.guarch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.