DPDK patches and discussions
 help / color / mirror / Atom feed
From: Neil Horman <nhorman@tuxdriver.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, neil.horman@tuxdriver.com
Subject: Re: [dpdk-dev] [PATCH v2 0/4] fix compilation on Fedora 22
Date: Fri, 29 May 2015 12:57:55 -0400	[thread overview]
Message-ID: <20150529165755.GD29575@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1432910056-6946-1-git-send-email-bruce.richardson@intel.com>

On Fri, May 29, 2015 at 03:34:12PM +0100, Bruce Richardson wrote:
> V2 Changes: 
> * use RTE_MIN instead of additional comparison checks
>   in some loops, as suggested by Neil.
> * For stats reset in null PMD, just use the size of the
>   array [which is 1] in place of the used queue counts.
> 
> GCC version 5.1 included with Fedora 22 is running stricter array 
> bounds checks which are throwing up errors in a number of components 
> in the DPDK code. This patchset fixes these errors to allow compilation
> with GCC on Fedora 22.
> 
> Example error:
> == Build lib/librte_eal/linuxapp/eal
>   CC eal_memory.o
> /home/bruce/dpdk.org/lib/librte_eal/linuxapp/eal/eal_memory.c: In function 'rte_eal_hugepage_init':
> /home/bruce/dpdk.org/lib/librte_eal/linuxapp/eal/eal_memory.c:1193:35: error: array subscript is above array bounds [-Werror=array-bounds]
>       internal_config.hugepage_info[j].hugepage_sz) {
>                                    ^
> compilation terminated due to -Wfatal-errors.
> 
> Bruce Richardson (4):
>   eal: fix compile on Fedora 22 (GCC 5.1)
>   ip_frag: fix compile on Fedora 22 (GCC 5.1)
>   i40e: fix compile on Fedora 22 (GCC 5.1)
>   null: fix compile on Fedora 22 (GCC 5.1)
> 
>  drivers/net/i40e/i40e_fdir.c             |  2 +-
>  drivers/net/null/rte_eth_null.c          | 12 ++++++++----
>  lib/librte_eal/linuxapp/eal/eal_memory.c |  4 +++-
>  lib/librte_ip_frag/ip_frag_common.h      |  2 +-
>  4 files changed, 13 insertions(+), 7 deletions(-)
> 
> -- 
> 2.4.1
> 
> 

Series
Acked-by: Neil Horman <nhorman@tuxdriver.com>

  parent reply	other threads:[~2015-05-29 16:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 12:53 [dpdk-dev] [PATCH " Bruce Richardson
2015-05-29 12:53 ` [dpdk-dev] [PATCH 1/4] eal: fix compile on Fedora 22 (GCC 5.1) Bruce Richardson
2015-05-29 14:07   ` Neil Horman
2015-05-29 12:53 ` [dpdk-dev] [PATCH 2/4] ip_frag: " Bruce Richardson
2015-05-29 14:09   ` Neil Horman
2015-05-29 12:53 ` [dpdk-dev] [PATCH 3/4] i40e: " Bruce Richardson
2015-05-29 12:53 ` [dpdk-dev] [PATCH 4/4] null: " Bruce Richardson
2015-05-29 14:34 ` [dpdk-dev] [PATCH v2 0/4] fix compilation on Fedora 22 Bruce Richardson
2015-05-29 14:34   ` [dpdk-dev] [PATCH v2 1/4] eal: fix compile on Fedora 22 (GCC 5.1) Bruce Richardson
2015-05-29 14:34   ` [dpdk-dev] [PATCH v2 2/4] ip_frag: " Bruce Richardson
2015-05-29 14:34   ` [dpdk-dev] [PATCH v2 3/4] i40e: " Bruce Richardson
2015-05-29 14:34   ` [dpdk-dev] [PATCH v2 4/4] null: " Bruce Richardson
2015-05-29 16:57   ` Neil Horman [this message]
2015-06-03 14:13     ` [dpdk-dev] [PATCH v2 0/4] fix compilation on Fedora 22 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=20150529165755.GD29575@hmsreliant.think-freely.org \
    --to=nhorman@tuxdriver.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=neil.horman@tuxdriver.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).