From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1639] GCC might generate Intel® AVX instructions for processors without Intel® AVX support
Date: Mon, 03 Feb 2025 03:07:12 +0000 [thread overview]
Message-ID: <bug-1639-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1639
Bug ID: 1639
Summary: GCC might generate Intel® AVX instructions for
processors without Intel® AVX support
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
When compiling DPDK (and any DPDK app), gcc may generate Intel® AVX
instructions, even when the processor does not support Intel® AVX.
Implication:
Any DPDK app might crash while starting up.
Resolution/Workaround:
Either compile using icc or set EXTRA_CFLAGS='-O3' prior to compilation.
Affected Environment/Platform:
Platforms which processor does not support Intel® AVX.
Driver/Module:
Environment Abstraction Layer (EAL).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2953 bytes --]
reply other threads:[~2025-02-03 3:07 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-1639-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).