From: Kevin Traynor <ktraynor@redhat.com>
To: Haiyue Wang <haiyue.wang@intel.com>,
dev@dpdk.org, bruce.richardson@intel.com,
konstantin.ananyev@intel.com, ian.stokes@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] eal: ignore alignment warnings for x86 vector
Date: Wed, 29 Apr 2020 09:40:36 +0100 [thread overview]
Message-ID: <88e5298d-9819-84b8-cfbe-d6822d0f8bc5@redhat.com> (raw)
In-Reply-To: <20200429064906.11496-1-haiyue.wang@intel.com>
On 29/04/2020 07:49, Haiyue Wang wrote:
> There several alignment warnings when including rte_memcpy header file
> externally like OVS for x86.
>
> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
> ---
> v2: Use __GUNC__ macro to apply for suppressing the warning.
> ---
> lib/librte_eal/x86/include/rte_memcpy.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/lib/librte_eal/x86/include/rte_memcpy.h b/lib/librte_eal/x86/include/rte_memcpy.h
> index ba44c4a32..d4cfe8dd5 100644
> --- a/lib/librte_eal/x86/include/rte_memcpy.h
> +++ b/lib/librte_eal/x86/include/rte_memcpy.h
> @@ -22,6 +22,10 @@
> extern "C" {
> #endif
>
> +#ifdef __GNUC__
> +#pragma GCC diagnostic ignored "-Wcast-align"
> +#endif
> +
Hi - have a look at this thread and the comments about a similar topic,
they are relevant here too.
http://inbox.dpdk.org/dev/20200416184549.10747-1-ktraynor@redhat.com/
> /**
> * Copy bytes from one location to another. The locations must not overlap.
> *
>
next prev parent reply other threads:[~2020-04-29 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 5:26 [dpdk-dev] [PATCH v1] eal: ignore alignment warnings for x86 Haiyue Wang
2020-04-29 6:49 ` [dpdk-dev] [PATCH v2] eal: ignore alignment warnings for x86 vector Haiyue Wang
2020-04-29 8:29 ` Wang, Haiyue
2020-04-29 8:40 ` Kevin Traynor [this message]
2020-04-29 16:17 ` Wang, Haiyue
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=88e5298d-9819-84b8-cfbe-d6822d0f8bc5@redhat.com \
--to=ktraynor@redhat.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=ian.stokes@intel.com \
--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).