From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: Lance Richardson <lance.richardson@broadcom.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] Build failures in 21.11-rc2
Date: Tue, 9 Nov 2021 17:44:04 +0100 [thread overview]
Message-ID: <47ba7d2c-b3ad-4a05-5552-06422446946f@intel.com> (raw)
In-Reply-To: <CADyeNECRhuRy1e88HwKp0fU_KZYqTfgmvC45awwNriJgNReSxQ@mail.gmail.com>
Hi all,
It looks like the problem caused by the lack of _mm512_set1_epi8()
implementation inside the gcc8, however _mm512_set1_epi[16,32,64] has
been implemented.
I replaced it with _mm512_set1_epi32 and on gcc8 it builds fine. I'll
send a fix soon.
On 09/11/2021 17:22, Lance Richardson wrote:
> Based on the CI build logs, the target architecture was Skylake, which
> supports AVX512 but doesn't support GFNI.
>
> On Tue, Nov 9, 2021 at 11:15 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>>
>> 09/11/2021 17:12, Lance Richardson:
>>> Do the machines used for the CentOS 8 CI builds support AVX512?
>>
>> Probably not. OK thank you.
>>
>>> The failing build is on an Ice Lake server with:
>>> meson -Dmachine=native build
>>> ninja -C build
>>>
>>> On Tue, Nov 9, 2021 at 11:08 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>>>> 09/11/2021 16:57, David Marchand:
>>>>> On Tue, Nov 9, 2021 at 4:53 PM Lance Richardson
>>>>> <lance.richardson@broadcom.com> wrote:
>>>>>>
>>>>>> 21.11-rc2 builds are failing on CentOS 8.4, apparently because
>>>>>> the intrinsic _mm512_set_epi8() is not defined in the GCC
>>>>>> headers (see example below).
>>>>>
>>>>> Thanks for reporting Lance.
>>>>> It rings a bell, think it was mentionned in the past.
>>>>
>>>> CI compilation was passing:
>>>> http://mails.dpdk.org/archives/test-report/2021-November/238534.html
>>>> I would like to better understand.
>>>>
>>>> [...]
>>>>>> Here is a GCC patch to add this intrinsic:
>>>>>> https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg188664.html
>>>>>>
>>>>>> BTW, GCC 10.2.1 (via "scl enable gcc-toolset-10") is able to build
>>>>>> 21.11-rc2 successfully on CentOS 8.4.
>>>>>>
>>>>>> Lance
>>>>>>
>>>>>> # gcc --version
>>>>>> gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
>>>> [...]
>>>>>> ../lib/hash/rte_thash_x86_gfni.h:59:24: error: implicit declaration of
>>>>>> function ‘_mm512_set_epi8’; did you mean ‘_mm512_set1_epi8’?
>>>>
>>>> What is different in your setup compared to the CI?
>>
>>
>>
--
Regards,
Vladimir
prev parent reply other threads:[~2021-11-09 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 15:53 Lance Richardson
2021-11-09 15:57 ` David Marchand
2021-11-09 16:08 ` Thomas Monjalon
2021-11-09 16:12 ` Lance Richardson
2021-11-09 16:15 ` Thomas Monjalon
2021-11-09 16:22 ` Lance Richardson
2021-11-09 16:44 ` Medvedkin, Vladimir [this message]
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=47ba7d2c-b3ad-4a05-5552-06422446946f@intel.com \
--to=vladimir.medvedkin@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=lance.richardson@broadcom.com \
--cc=thomas@monjalon.net \
/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).