From: Andre Muezerie <andremue@linux.microsoft.com>
To: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
"Tyler Retzlaff" <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, Andre Muezerie <andremue@linux.microsoft.com>
Subject: [PATCH 1/6] eal: make compatible with instruction set updates for MSVC
Date: Mon, 24 Feb 2025 13:01:14 -0800 [thread overview]
Message-ID: <1740430879-17874-2-git-send-email-andremue@linux.microsoft.com> (raw)
In-Reply-To: <1740430879-17874-1-git-send-email-andremue@linux.microsoft.com>
After the instruction set updates for MSVC the error below poped up:
../lib/eal/common/rte_random.c(6): fatal error C1083:
Cannot open include file: 'x86intrin.h': No such file or directory
The fix is to not include header x86intrin.h with MSVC.
Signed-off-by: Andre Muezerie <andremue@linux.microsoft.com>
---
lib/eal/common/rte_random.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/eal/common/rte_random.c b/lib/eal/common/rte_random.c
index 8e62578176..9354358818 100644
--- a/lib/eal/common/rte_random.c
+++ b/lib/eal/common/rte_random.c
@@ -3,8 +3,10 @@
*/
#ifdef __RDSEED__
+#ifndef RTE_TOOLCHAIN_MSVC
#include <x86intrin.h>
#endif
+#endif
#include <unistd.h>
#include <rte_bitops.h>
--
2.48.1.vfs.0.0
next prev parent reply other threads:[~2025-02-24 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 21:01 [PATCH 0/6] allow faster instruction sets to be used with MSVC Andre Muezerie
2025-02-24 21:01 ` Andre Muezerie [this message]
2025-02-24 21:01 ` [PATCH 2/6] eal: only use numbers as align parameters for MSVC Andre Muezerie
2025-02-24 21:01 ` [PATCH 3/6] config: allow faster instruction sets to be used with MSVC Andre Muezerie
2025-02-24 21:01 ` [PATCH 4/6] drivers/net: make compatible with instruction set updates for MSVC Andre Muezerie
2025-02-24 21:01 ` [PATCH 5/6] acl: " Andre Muezerie
2025-02-24 21:01 ` [PATCH 6/6] member: " Andre Muezerie
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=1740430879-17874-2-git-send-email-andremue@linux.microsoft.com \
--to=andremue@linux.microsoft.com \
--cc=dev@dpdk.org \
--cc=mattias.ronnblom@ericsson.com \
--cc=roretzla@linux.microsoft.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).