From: Thomas Monjalon <thomas@monjalon.net>
To: liangma@liangbit.com, Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] acl: fix build with GCC 6.3
Date: Fri, 21 May 2021 17:10:41 +0200 [thread overview]
Message-ID: <5942248.XgMt1RgFVE@thomas> (raw)
In-Reply-To: <20210521144207.13802-1-konstantin.ananyev@intel.com>
21/05/2021 16:42, Konstantin Ananyev:
> --buildtype=debug with gcc 6.3 produces the following error:
>
> ../lib/librte_acl/acl_run_avx512_common.h: In function
> ‘resolve_match_idx_avx512x16’:
> ../lib/librte_acl/acl_run_avx512x16.h:33:18: error:
> the last argument must be an 8-bit immediate
> ^
> ../lib/librte_acl/acl_run_avx512_common.h:373:9: note:
> in expansion of macro ‘_M_I_’
> return _M_I_(slli_epi32)(mi, match_log);
> ^~~~~
>
> Seems like gcc-6.3 complains about the following construct:
>
> static const uint32_t match_log = 5;
> ...
> _mm512_slli_epi32(mi, match_log);
>
> It can't substitute constant variable 'match_log' with its actual value.
> The fix replaces constant variable with its immediate value.
>
> Bugzilla ID: 717
> Fixes: b64c2295f7fc ("acl: add 256-bit AVX512 classify method")
> Fixes: 45da22e42ec3 ("acl: add 512-bit AVX512 classify method")
> Cc: stable@dpdk.org
>
> Reported-by: Liang Ma <liangma@liangbit.com>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
How much critical is it?
It looks safer to wait for 21.08 cycle?
next prev parent reply other threads:[~2021-05-21 15:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 14:42 [dpdk-dev] [PATCH] acl: fix build with GCC 6.3 Konstantin Ananyev
2021-05-21 14:55 ` Liang Ma
2021-05-21 15:10 ` Thomas Monjalon [this message]
2021-05-21 15:16 ` Ananyev, Konstantin
2021-05-21 15:21 ` Liang Ma
2021-06-17 6:57 ` 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=5942248.XgMt1RgFVE@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=liangma@liangbit.com \
--cc=stable@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.