DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
To: "Mrzyglod, DanielX T" <danielx.t.mrzyglod@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mk: add support for ICC 15 compiler
Date: Fri, 23 Jan 2015 10:49:15 +0000	[thread overview]
Message-ID: <91383E96CE459D47BCE92EFBF5CE73B004F42697@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1421920442-7804-1-git-send-email-danielx.t.mrzyglod@intel.com>

> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Daniel Mrzyglod
> Sent: Thursday, January 22, 2015 9:54 AM
> 
> This patch add Support for ICC 15.
> 
> ICC 15 changed inline-max-size and inline-max-total-size default values, so
> for ICC 15 flags -no-inline-max-size -no-inline-max-total-size must be added.
> 
> additionally disable compile error for:
> 13368 - loop was not vectorized with "vector always assert"
> 15527 - loop was not vectorized: function call to fprintf cannot be vectorize
> 
> Signed-off-by: Daniel Mrzyglod <danielx.t.mrzyglod@intel.com>
> ---
>  mk/toolchain/icc/rte.vars.mk | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/mk/toolchain/icc/rte.vars.mk b/mk/toolchain/icc/rte.vars.mk
> index 5503fb0..e39d710 100644
> --- a/mk/toolchain/icc/rte.vars.mk
> +++ b/mk/toolchain/icc/rte.vars.mk
> @@ -66,11 +66,18 @@ TOOLCHAIN_ASFLAGS =
>  # Turn off some ICC warnings -
>  #   Remark #271   : trailing comma is nonstandard
>  #   Warning #1478 : function "<func_name>" (declared at line N of
> "<filename>")
> +#   error #13368: loop was not vectorized with "vector always assert"
> +#   error #15527: loop was not vectorized: function call to fprintf cannot be
> vectorize
>  #                   was declared "deprecated"
>  WERROR_FLAGS := -Wall -Werror-all -w2 -diag-disable 271 -diag-warning
> 1478
> +WERROR_FLAGS += -diag-disable 13368 -diag-disable 15527
> 
>  # process cpu flags
>  include $(RTE_SDK)/mk/toolchain/$(RTE_TOOLCHAIN)/rte.toolchain-
> compat.mk
> +# disable max-inline params boundaries for ICC 15 compiler ifeq
> +($(shell test $(ICC_MAJOR_VERSION) -eq 15 && echo 1), 1)
> +	TOOLCHAIN_CFLAGS += -no-inline-max-size -no-inline-max-total-size
> +endif
> 
>  export CC AS AR LD OBJCOPY OBJDUMP STRIP READELF  export
> TOOLCHAIN_CFLAGS TOOLCHAIN_LDFLAGS TOOLCHAIN_ASFLAGS
> --
> 2.1.0

Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>

  reply	other threads:[~2015-01-23 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  9:54 Daniel Mrzyglod
2015-01-23 10:49 ` Gonzalez Monroy, Sergio [this message]
2015-01-27 11:16   ` 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=91383E96CE459D47BCE92EFBF5CE73B004F42697@IRSMSX108.ger.corp.intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=danielx.t.mrzyglod@intel.com \
    --cc=dev@dpdk.org \
    /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).