From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Reshma Pattan <reshma.pattan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3] mk: gcc -march support for intel processors code names
Date: Wed, 12 Oct 2016 14:33:48 +0200 [thread overview]
Message-ID: <2355225.oGVz1zBJsg@xps13> (raw)
In-Reply-To: <1476135193-4721-1-git-send-email-reshma.pattan@intel.com>
2016-10-10 22:33, Reshma Pattan:
> The GCC 4.9 -march option supports the intel code names for processors,
> for example -march=silvermont, -march=broadwell.
> The RTE_MACHINE config flag can be used to pass code name to
> the compiler as -march flag.
>
> Release notes is updated.
>
> Linux and FreeBSD getting started guides are updated with recommended
> gcc version as 4.9 and above.
>
> Some of the gmake command examples in sample application guide and driver
> guides are updated with gcc version as 4.9.
>
> Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
Applied, thanks
How the -march=broadwell option will work with icc and clang?
next prev parent reply other threads:[~2016-10-12 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 15:02 [PATCH] mk: gcc -march support for intel processors code names Reshma Pattan
2016-08-22 11:25 ` Thomas Monjalon
2016-08-22 11:46 ` Pattan, Reshma
2016-08-22 12:36 ` Thomas Monjalon
2016-09-05 3:24 ` Liu, Yong
2016-08-22 14:19 ` [PATCH v2] " Reshma Pattan
2016-09-02 14:17 ` Pattan, Reshma
2016-09-28 10:21 ` [dpdk-dev, " Remy Horton
2016-09-29 1:11 ` Liu, Yong
2016-10-10 21:33 ` [PATCH v3] " Reshma Pattan
2016-10-12 12:33 ` Thomas Monjalon [this message]
2016-10-12 13:38 ` Pattan, Reshma
2016-10-12 14:20 ` 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=2355225.oGVz1zBJsg@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@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.