From: sys_stv@intel.com
To: test-report@dpdk.org, andremue@linux.microsoft.com
Subject: compilation|WARNING| pw(150453) sid(31576) job(PER_PATCH_BUILD14696)[v3, 3/3] app/test: add test for rte_ffs32 and rte_ffs64 functions.
Date: 24 Jan 2025 08:22:35 -0800 [thread overview]
Message-ID: <330255$3bmjjc@orviesa005-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Test-Label: Intel-compilation
Test-Status: WARNING
http://dpdk.org/patch/150453
_apply issues_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: 2025-01-24 16:14:04
Reply_mail: <1737735244-23234-4-git-send-email-andremue@linux.microsoft.com>
DPDK git baseline:
Repo:dpdk, CommitID: 5b856206c74bbcf19e12cafa15382a7e15b0a1b5
* Repo: dpdk
eal/x86: fix some intrinsics header include for Windows
Error reported:
../lib/net/net_crc_sse.c:49:17: error: call to undeclared function
'_mm_clmulepi64_si128'; ISO C99 and later do not support implicit
function declarations [-Wimplicit-function-declaration]
--
Server version missing
You should provide the server version in the URL configured via git-config or --server
This will be required in git-pw 2.0
error: patch failed: lib/eal/x86/include/rte_io.h:22
error: lib/eal/x86/include/rte_io.h: patch does not apply
Applying: eal: provide movdiri for MSVC
Patch failed at 0001 eal: provide movdiri for MSVC
Use 'git am --show-current-patch' to see the failed patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
DPDK STV team
reply other threads:[~2025-01-24 16:22 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='330255$3bmjjc@orviesa005-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=andremue@linux.microsoft.com \
--cc=test-report@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).