[dpdk-dev] [PATCH v3 04/12] eal: allow empty compile time flags

2015-07-09 Thread damu
-- Original -- From: "Tony Lu";; Date: Jul 9, 2015 To: "'Thomas Monjalon'"; Cc: "dev"; Subject: Re: [dpdk-dev] [PATCH v3 04/12] eal: allow empty compile time flags >-Original Message- >From: Thomas

[dpdk-dev] [PATCH v3 04/12] eal: allow empty compile time flags

2015-07-09 Thread Tony Lu
>-Original Message- >From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] >Sent: Thursday, July 09, 2015 8:46 AM >To: Zhigang Lu >Cc: dev at dpdk.org >Subject: Re: [dpdk-dev] [PATCH v3 04/12] eal: allow empty compile time flags > >2015-07-06 1

[dpdk-dev] [PATCH v3 04/12] eal: allow empty compile time flags

2015-07-09 Thread Thomas Monjalon
2015-07-06 16:51, Zhigang Lu: > The rte_cpu_check_supported() code breaks with a "comparison is always > false due to limited range of data type" when the compile_time_flags[] > array is empty. Assigning the array dimension to a local variable > apparently solves this. How is it related to the ti

[dpdk-dev] [PATCH v3 04/12] eal: allow empty compile time flags

2015-07-06 Thread Zhigang Lu
The rte_cpu_check_supported() code breaks with a "comparison is always false due to limited range of data type" when the compile_time_flags[] array is empty. Assigning the array dimension to a local variable apparently solves this. Change-Id: I0ae21f529cf7b6dd9cf0f4532dce9198f4bf4230 Signed-off-b

[dpdk-dev] [PATCH v3 04/12] eal: allow empty compile time flags

2015-07-06 Thread Bruce Richardson
On Mon, Jul 06, 2015 at 04:51:29PM +0800, Zhigang Lu wrote: > The rte_cpu_check_supported() code breaks with a "comparison is always > false due to limited range of data type" when the compile_time_flags[] > array is empty. Assigning the array dimension to a local variable > apparently solves this