patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	stable@dpdk.org, Tom Barbette <barbette@kth.se>,
	Yongseok Koh <yskoh@mellanox.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>,
	Vipin Varghese <vipin.varghese@intel.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v5] mk: fix scope of disabling AVX512F support
Date: Mon, 14 Jan 2019 17:28:56 +0100	[thread overview]
Message-ID: <2013296.yFTJKXJfz1@xps> (raw)
In-Reply-To: <20190114154935.6072-1-ferruh.yigit@intel.com>

14/01/2019 16:49, Ferruh Yigit:
> AVX512 was disabled for GCC because of Bugzilla issue 97 [1],
> the GCC defect submitted for the issue [2] highlighted that this is
> a known binutils version 2.30 issue.
> 
> Narrowed the scope of no-avx512 to the this specific binutils version.
> 
> [1]
> https://bugs.dpdk.org/show_bug.cgi?id=97
> 
> [2]
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88096
> 
> Fixes: 8d07c82b239f ("mk: disable gcc AVX512F support")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> Cc: Tom Barbette <barbette@kth.se>
> Cc: Thomas Monjalon <thomas@monjalon.net>
> Cc: Yongseok Koh <yskoh@mellanox.com>
> Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Cc: Bruce Richardson <bruce.richardson@intel.com>
> 
> v2:
> * Added warning message (print only once for eal)
> * Moved decision details to compat file, kept execution in cpuflags
> 
> v3:
> * replace 'ld' with '$(LD)' for cross build
> * added meson support
> 
> v4:
> * Document this limitation in release notes
> Cc: Vipin Varghese <vipin.varghese@intel.com>
> 
> v5:
> * Grammar fix
> * remove $(lastword.. ) from makefile
> * add 'OR' between possible workarounds

Acked-by: Thomas Monjalon <thomas@monjalon.net>

Applied, thanks

      reply	other threads:[~2019-01-14 16:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-19 19:29 [dpdk-stable] [PATCH] " Ferruh Yigit
2018-12-19 19:58 ` Thomas Monjalon
2018-12-19 20:20   ` Ferruh Yigit
2018-12-19 20:28     ` Thomas Monjalon
2018-12-19 20:53       ` Ferruh Yigit
2018-12-20 11:29         ` Bruce Richardson
2018-12-19 21:00 ` [dpdk-stable] [PATCH v2] " Ferruh Yigit
2018-12-22 23:02   ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2019-01-03 16:23   ` [dpdk-stable] [PATCH v3] " Ferruh Yigit
2019-01-03 22:46     ` Yongseok Koh
2019-01-04  2:40       ` Varghese, Vipin
2019-01-04 10:27         ` Ferruh Yigit
2019-01-04 10:28           ` Varghese, Vipin
2019-01-07 16:49     ` [dpdk-stable] [PATCH v4] " Ferruh Yigit
2019-01-08  3:50       ` Varghese, Vipin
2019-01-14 11:55       ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2019-01-14 15:49       ` [dpdk-stable] [PATCH v5] " Ferruh Yigit
2019-01-14 16:28         ` Thomas Monjalon [this message]

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=2013296.yFTJKXJfz1@xps \
    --to=thomas@monjalon.net \
    --cc=barbette@kth.se \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=stable@dpdk.org \
    --cc=vipin.varghese@intel.com \
    --cc=yskoh@mellanox.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).