From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 344] Broken CPU feature discovery for armv8
Date: Wed, 04 Sep 2019 12:43:56 +0000 [thread overview]
Message-ID: <bug-344-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=344
Bug ID: 344
Summary: Broken CPU feature discovery for armv8
Product: DPDK
Version: unspecified
Hardware: ARM
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: i.maximets@samsung.com
Target Milestone: ---
To check available cpuflags both build systems (make and meson) uses compiler
invocations with provided machine flags which is '-march=armv8-a+crc'.
It makes no much sense getting defines from the cc with non-native arch as
it will have nothing common with real cpu features available.
This leads to inability using dpdk on armv8 platform without crc support due
to illegal instructions.
'-march=native' is only available since GCC 8. Also, DPDK uses
'-march=armv8-a+crc'
as a default armv8 machine regardless of fact that crc extension is optional.
Reported-at:
https://mail.openvswitch.org/pipermail/ovs-dev/2019-September/362301.html
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-09-04 12:43 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-344-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 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.