DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Olga Shern <olgas@mellanox.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: work around compilation issue
Date: Fri, 15 Jul 2016 23:00:40 +0200	[thread overview]
Message-ID: <4351464.EB90HY8EQ2@xps13> (raw)
In-Reply-To: <1468420402-27477-1-git-send-email-adrien.mazarguil@6wind.com>

2016-07-13 16:33, Adrien Mazarguil:
> From: Olga Shern <olgas@mellanox.com>
> 
> RHEL 7.1's GCC for POWER8 reports the following error in one rte_memcpy()
> macro call by mlx5:
> 
>  error: array subscript is above array bounds [-Werror=array-bounds]
> 
> It appears to be a GCC bug which can be worked around by making parentheses
> more explicit.
> 
> Signed-off-by: Olga Shern <olgas@mellanox.com>
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

Applied, thanks

      reply	other threads:[~2016-07-15 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 14:33 Adrien Mazarguil
2016-07-15 21:00 ` Thomas Monjalon [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=4351464.EB90HY8EQ2@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=olgas@mellanox.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).