From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: keith.wiles@intel.com
Cc: dev@dpdk.org, henning.schild@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [dpdk-dev] [PATCH] Add build option to enable/disable AVX2 support
Date: Mon, 26 Oct 2020 15:30:27 +0100 [thread overview]
Message-ID: <20201026143027.15246-1-felix.moessbauer@siemens.com> (raw)
This patch introduces a meson option to disable the AVX2 support.
If the build should be for a target without AVX2 support, the
know can be turned to false, even if the compiler supports AVX2.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
meson.build | 3 ++-
meson_options.txt | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 0ee98be..2e2380c 100644
--- a/meson.build
+++ b/meson.build
@@ -18,7 +18,8 @@ pktgen_conf = configuration_data()
cc = meson.get_compiler('c')
add_project_arguments('-march=native', language: 'c')
-if cc.has_argument('-mavx2')
+
+if get_option('enable-avx2') and cc.has_argument('-mavx2')
add_project_arguments('-mavx2', language: 'c')
endif
add_project_arguments('-DALLOW_EXPERIMENTAL_API', language: 'c')
diff --git a/meson_options.txt b/meson_options.txt
index 7b42577..c419517 100644
--- a/meson_options.txt
+++ b/meson_options.txt
@@ -1,3 +1,4 @@
option('enable_lua', type: 'boolean', value: false, description: 'Enable Lua support')
option('enable_gui', type: 'boolean', value: false, description: 'build the gui')
option('enable_docs', type: 'boolean', value: false, description: 'build documentation')
+option('enable-avx2', type: 'boolean', value: true, description: 'compile with AVX2 support')
--
2.20.1
next reply other threads:[~2020-10-26 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 14:30 Felix Moessbauer [this message]
2020-10-27 11:47 ` Bruce Richardson
2020-10-29 13:36 ` Wiles, Keith
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=20201026143027.15246-1-felix.moessbauer@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=dev@dpdk.org \
--cc=henning.schild@siemens.com \
--cc=keith.wiles@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).