From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [PATCH] doc: announce disabling GCC AVX512F as known issue
Date: Tue, 20 Nov 2018 12:50:31 +0000 [thread overview]
Message-ID: <20181120125031.3390-1-ferruh.yigit@intel.com> (raw)
Document that AVX512F has been disabled for GCC builds [1] and document
its potential implications on release notes, known issue section.
[1]
Commit 8d07c82b239f ("mk: disable gcc AVX512F support")
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
doc/guides/rel_notes/release_18_11.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/guides/rel_notes/release_18_11.rst b/doc/guides/rel_notes/release_18_11.rst
index 32ff0e5c0..1116aff57 100644
--- a/doc/guides/rel_notes/release_18_11.rst
+++ b/doc/guides/rel_notes/release_18_11.rst
@@ -567,6 +567,17 @@ Known Issues
* IBM Power8 is not supported by this release of DPDK. IBM Power9 is supported.
+* ``AVX-512`` support has been disabled for ``GCC`` builds [1] because of a crash [2].
+ This can affect ``native`` machine type build targets on the platforms that support
+ ``AVX512F`` like ``Intel Skylake`` processors, and can cause a possible performance drop.
+ The immediate workaround is to use ``clang`` compiler on these platforms.
+ Issue has been identified as a GCC defect and reported to GCC community [3]. Further
+ actions will be taken based on the GCC defect result.
+
+ [1]: Commit 8d07c82b239f ("mk: disable gcc AVX512F support")
+ [2]: https://bugs.dpdk.org/show_bug.cgi?id=97
+ [3]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88096
+
Tested Platforms
----------------
--
2.17.2
next reply other threads:[~2018-11-20 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 12:50 Ferruh Yigit [this message]
2018-11-22 18:00 ` Mcnamara, John
2018-11-23 2:02 ` 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=20181120125031.3390-1-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=marko.kovacevic@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).