From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1736] building DPDK [v25.07-rc2] error: inlining failed in call to always_inline ‘_mm512_clmulepi64_epi128’: target specific option mismatch _mm512_clmulepi64_epi128 (__m512i __A, __m512i __B, const int __C)
Date: Wed, 02 Jul 2025 08:02:43 +0000 [thread overview]
Message-ID: <bug-1736-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 2844 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1736
Bug ID: 1736
Summary: building DPDK [v25.07-rc2] error: inlining failed in
call to always_inline ‘_mm512_clmulepi64_epi128’:
target specific option mismatch
_mm512_clmulepi64_epi128 (__m512i __A, __m512i __B,
const int __C)
Product: DPDK
Version: 25.03
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: meson
Assignee: dev@dpdk.org
Reporter: 14pwcse1224@uetpeshawar.edu.pk
Target Milestone: ---
/usr/lib/gcc/x86_64-redhat-linux/8/include/avx512fintrin.h:1579:1: error:
inlining failed in call to always_inline ‘_mm512_ternarylogic_epi64’: target
specific option mismatch
_mm512_ternarylogic_epi64 (__m512i __A, __m512i __B, __m512i __C,
^~~~~~~~~~~~~~~~~~~~~~~~~
../lib/net/net_crc_avx512.c:56:9: note: called from here
return _mm512_ternarylogic_epi64(tmp0, tmp1, data_block, 0x96);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/usr/lib/gcc/x86_64-redhat-linux/8/include/immintrin.h:111,
from
/usr/lib/gcc/x86_64-redhat-linux/8/include/x86intrin.h:48,
from ../lib/eal/x86/include/rte_vect.h:24,
from ../lib/net/net_crc_avx512.c:8:
/usr/lib/gcc/x86_64-redhat-linux/8/include/vpclmulqdqintrin.h:40:1: error:
inlining failed in call to always_inline ‘_mm512_clmulepi64_epi128’: target
specific option mismatch
_mm512_clmulepi64_epi128 (__m512i __A, __m512i __B, const int __C)
^~~~~~~~~~~~~~~~~~~~~~~~
../lib/net/net_crc_avx512.c:54:9: note: called from here
tmp1 = _mm512_clmulepi64_epi128(fold, precomp, 0x10);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from
/usr/lib/gcc/x86_64-redhat-linux/8/include/immintrin.h:111,
from
/usr/lib/gcc/x86_64-redhat-linux/8/include/x86intrin.h:48,
from ../lib/eal/x86/include/rte_vect.h:24,
from ../lib/net/net_crc_avx512.c:8:
/usr/lib/gcc/x86_64-redhat-linux/8/include/vpclmulqdqintrin.h:40:1: error:
inlining failed in call to always_inline ‘_mm512_clmulepi64_epi128’: target
specific option mismatch
_mm512_clmulepi64_epi128 (__m512i __A, __m512i __B, const int __C)
^~~~~~~~~~~~~~~~~~~~~~~~
../lib/net/net_crc_avx512.c:53:9: note: called from here
tmp0 = _mm512_clmulepi64_epi128(fold, precomp, 0x01);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[142/3483] Compiling C object lib/librte_ethdev.a.p/ethdev_rte_ethdev.c.o
ninja: build stopped: subcommand failed.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4794 bytes --]
reply other threads:[~2025-07-02 8:02 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-1736-3@https.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.