dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] A fix to work around strict-aliasing rules breaking
Date: Thu, 05 Mar 2015 18:33:46 +0100	[thread overview]
Message-ID: <1492500.Ex1SnWRXJA@xps13> (raw)
In-Reply-To: <1425287030-18225-1-git-send-email-zhihong.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>

2015-03-02 17:03, zhihong.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org:
> Fixed strict-aliasing rules breaking errors for some GCC version.
> 
> Signed-off-by: Zhihong Wang <zhihong.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> ---
>  .../common/include/arch/x86/rte_memcpy.h           | 44 ++++++++++++----------
>  1 file changed, 24 insertions(+), 20 deletions(-)
> 
> diff --git a/lib/librte_eal/common/include/arch/x86/rte_memcpy.h b/lib/librte_eal/common/include/arch/x86/rte_memcpy.h
> index 69a5c6f..f412099 100644
> --- a/lib/librte_eal/common/include/arch/x86/rte_memcpy.h
> +++ b/lib/librte_eal/common/include/arch/x86/rte_memcpy.h
> @@ -195,6 +195,8 @@ rte_mov256blocks(uint8_t *dst, const uint8_t *src, size_t n)
>  static inline void *
>  rte_memcpy(void *dst, const void *src, size_t n)
>  {
> +	uintptr_t dstu = (uintptr_t)dst;
> +	uintptr_t srcu = (uintptr_t)src;
>  	void *ret = dst;
>  	int dstofss;
>  	int bits;
> @@ -204,22 +206,22 @@ rte_memcpy(void *dst, const void *src, size_t n)
>  	 */
>  	if (n < 16) {
>  		if (n & 0x01) {
> -			*(uint8_t *)dst = *(const uint8_t *)src;
> -			src = (const uint8_t *)src + 1;
> -			dst = (uint8_t *)dst + 1;
> +			*(uint8_t *)dstu = *(const uint8_t *)srcu;
> +			srcu = (uintptr_t)((const uint8_t *)srcu + 1);
> +			dstu = (uintptr_t)((uint8_t *)dstu + 1);
[...]

Is there another solution?
Are we going to acknowledge this fix?

  parent reply	other threads:[~2015-03-05 17:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02  9:03 [PATCH] A fix to work around strict-aliasing rules breaking zhihong.wang-ral2JQCrhuEAvxtiuMwx3w
     [not found] ` <1425287030-18225-1-git-send-email-zhihong.wang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-03-02 10:32   ` Bruce Richardson
2015-03-02 12:32     ` Pawel Wodkowski
     [not found]       ` <54F4584B.5090507-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-03-04  5:57         ` Wang, Zhihong
2015-03-04  2:07     ` Wang, Zhihong
     [not found]       ` <F60F360A2500CD45ACDB1D700268892D0E790DF6-0J0gbvR4kThpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-03-04 10:18         ` Bruce Richardson
2015-03-05 17:33   ` Thomas Monjalon [this message]
2015-03-06  7:36   ` Liang, Cunming
     [not found]     ` <54F958ED.4070800-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-03-09 11:44       ` Thomas Monjalon
2015-03-09  6:14 ` Qiu, Michael

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=1492500.Ex1SnWRXJA@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.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 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).