From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>
Cc: "Liu, Yong" <yong.liu@intel.com>, dev@dpdk.org
Subject: Re: [PATCH v2] mk: gcc -march support for intel processors code names
Date: Mon, 10 Oct 2016 19:09:39 +0200 [thread overview]
Message-ID: <3926568.66BEXk8PUy@xps13> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F010ADCFC@IRSMSX109.ger.corp.intel.com>
2016-10-10 15:21, Pattan, Reshma:
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Why not recommend GCC 4.9 and keep the graceful degradation for older
> > versions, at least for one more year, even if it is not optimal for newer
> > architectures?
>
> I am ok with the idea, so should I send latest patch by keeping the code in
> mk/toolchain/gcc/rte.toolchain-compat.mk untouched/intact?
Yes please.
next prev parent reply other threads:[~2016-10-10 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 2:54 [PATCH v2] mk: gcc -march support for intel processors code names Liu, Yong
2016-10-10 14:25 ` Thomas Monjalon
2016-10-10 15:21 ` Pattan, Reshma
2016-10-10 17:09 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-15 15:02 [PATCH] " Reshma Pattan
2016-08-22 14:19 ` [PATCH v2] " Reshma Pattan
2016-09-02 14:17 ` Pattan, Reshma
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=3926568.66BEXk8PUy@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@intel.com \
--cc=yong.liu@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.