DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] mk: gcc -march support for intel processors code names
Date: Mon, 22 Aug 2016 14:36:29 +0200	[thread overview]
Message-ID: <4688161.1QGC1dzfkE@xps13> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F010728ED@IRSMSX109.ger.corp.intel.com>

2016-08-22 11:46, Pattan, Reshma:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 2016-08-15 16:02, 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. Also old gcc versions compatibility code for
> > > the intel platform is removed from
> > > mk/toolchain/gcc/rte.toolchain-compat.mk
> > 
> > Do you mean to not support GCC < 4.9 ?
> 
> Yes. 

It can be discussed but you must, at least, update the requirements:
	http://dpdk.org/doc/guides/linux_gsg/sys_reqs.html#compilation-of-the-dpdk

  reply	other threads:[~2016-08-22 12:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 15:02 Reshma Pattan
2016-08-22 11:25 ` Thomas Monjalon
2016-08-22 11:46   ` Pattan, Reshma
2016-08-22 12:36     ` Thomas Monjalon [this message]
2016-09-05  3:24     ` Liu, Yong
2016-08-22 14:19 ` [dpdk-dev] [PATCH v2] " Reshma Pattan
2016-09-02 14:17   ` Pattan, Reshma
2016-09-28 10:21   ` [dpdk-dev] [dpdk-dev, " Remy Horton
2016-09-29  1:11     ` Liu, Yong
2016-10-10 21:33   ` [dpdk-dev] [PATCH v3] " Reshma Pattan
2016-10-12 12:33     ` Thomas Monjalon
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=4688161.1QGC1dzfkE@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 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).