From: Jan Viktorin <viktorin@rehivetech.com>
To: dev@dpdk.org
Cc: Jan Viktorin <viktorin@rehivetech.com>,
tomasz.kantecki@intel.com, maciej.czekaj@caviumnetworks.com,
tomaszx.kulasek@intel.com
Subject: [dpdk-dev] [PATCH] examples/l3fwd: report error when no vector engine is available
Date: Tue, 26 Apr 2016 13:30:59 +0200 [thread overview]
Message-ID: <1461670259-3339-1-git-send-email-viktorin@rehivetech.com> (raw)
If no SSE nor NEON are available the l3fwd should complain loudly to quickly
find out the reason.
Signed-off-by: Jan Viktorin <viktorin@rehivetech.com>
---
It has happened to me once when I've accidently built a GCC without the NEON
support. It was confusing as at first I thought it is a bug... It is not,
there is just missing an error message telling the reason.
---
examples/l3fwd/l3fwd_em.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/examples/l3fwd/l3fwd_em.c b/examples/l3fwd/l3fwd_em.c
index fc59243..259094d 100644
--- a/examples/l3fwd/l3fwd_em.c
+++ b/examples/l3fwd/l3fwd_em.c
@@ -259,6 +259,8 @@ em_mask_key(void *key, xmm_t mask)
return vandq_s32(data, mask);
}
+#else
+#error No vector engine (SSE, NEON) available, check your toolchain
#endif
static inline uint8_t
--
2.8.0
next reply other threads:[~2016-04-26 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 11:30 Jan Viktorin [this message]
2016-06-08 20:21 ` 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=1461670259-3339-1-git-send-email-viktorin@rehivetech.com \
--to=viktorin@rehivetech.com \
--cc=dev@dpdk.org \
--cc=maciej.czekaj@caviumnetworks.com \
--cc=tomasz.kantecki@intel.com \
--cc=tomaszx.kulasek@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).