From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1656] AVX-512 support disabled
Date: Mon, 03 Feb 2025 04:33:27 +0000 [thread overview]
Message-ID: <bug-1656-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1656
Bug ID: 1656
Summary: AVX-512 support disabled
Product: DPDK
Version: 18.11
Hardware: All
OS: Other
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
AVX-512 support has been disabled on some conditions.
On DPDK v18.11 AVX-512 is disabled for all GCC builds which reported to cause a
performance drop.
On DPDK v19.02 AVX-512 disable scope is reduced to GCC and binutils version
2.30 based on information accrued from the GCC community defect.
Reason:
Generated AVX-512 code cause crash: https://bugs.dpdk.org/show_bug.cgi?id=97
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88096
Resolution/Workaround:
Update binutils to newer version than 2.30.
OR
Use different compiler, like clang for this case.
Affected Environment/Platform:
GCC and binutils version 2.30.
Driver/Module:
ALL.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3297 bytes --]
reply other threads:[~2025-02-03 4:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1656-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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).