From: Ali Alnubani <alialnu@nvidia.com>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "alialnu@mellanox.com" <alialnu@mellanox.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] acl: fix build failure with gcc 5.4.0
Date: Thu, 15 Oct 2020 12:28:09 +0000 [thread overview]
Message-ID: <DM6PR12MB4618099AB627BF73549A844DDA020@DM6PR12MB4618.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20201015115356.28171-1-konstantin.ananyev@intel.com>
Thanks Konstantin.
> -----Original Message-----
> From: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Sent: Thursday, October 15, 2020 2:54 PM
> To: dev@dpdk.org
> Cc: alialnu@mellanox.com; david.marchand@redhat.com; Konstantin
> Ananyev <konstantin.ananyev@intel.com>
> Subject: [PATCH] acl: fix build failure with gcc 5.4.0
>
> gcc 5.4 fails with:
> ../lib/librte_acl/acl_run_avx512x8.h: In function 'match_process_avx512x8':
> ../lib/librte_acl/acl_run_avx512x8.h:382:31: error:
> pointer targets in passing argument 1 of '_mm256_mask_i32scatter_epi32'
> differ in signedness [-Werror=pointer-sign]
>
> Later gcc versions work fine, as for them parameter type was changed to
> 'void *'.
> Fixed by applying explicit cast for offending argument.
>
> Fixes: b64c2295f7fc ("acl: add 256-bit AVX512 classify method")
> Fixes: 45da22e42ec3 ("acl: add 512-bit AVX512 classify method")
>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> ---
Tested-by: Ali Alnubani <alialnu@nvidia.com>
- Ali
next prev parent reply other threads:[~2020-10-15 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 11:53 Konstantin Ananyev
2020-10-15 12:28 ` Ali Alnubani [this message]
2020-10-15 12:55 ` David Marchand
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=DM6PR12MB4618099AB627BF73549A844DDA020@DM6PR12MB4618.namprd12.prod.outlook.com \
--to=alialnu@nvidia.com \
--cc=alialnu@mellanox.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).