Re: [dpdk-dev] [PATCH v3 2/2] eal: fix signed integers in fbarray

2018-04-17 Thread Thomas Monjalon
17/04/2018 13:14, Burakov, Anatoly: > On 14-Apr-18 11:03 AM, Burakov, Anatoly wrote: > > On 13-Apr-18 7:43 PM, Adrien Mazarguil wrote: > >> While debugging startup issues encountered with Clang (see "eal: fix > >> undefined behavior in fbarray"), I noticed that fbarray stores indices, > >> sizes an

Re: [dpdk-dev] [PATCH v3 2/2] eal: fix signed integers in fbarray

2018-04-17 Thread Burakov, Anatoly
On 14-Apr-18 11:03 AM, Burakov, Anatoly wrote: On 13-Apr-18 7:43 PM, Adrien Mazarguil wrote: While debugging startup issues encountered with Clang (see "eal: fix undefined behavior in fbarray"), I noticed that fbarray stores indices, sizes and masks on signed integers involved in bitwise operati

Re: [dpdk-dev] [PATCH v3 2/2] eal: fix signed integers in fbarray

2018-04-14 Thread Burakov, Anatoly
On 13-Apr-18 7:43 PM, Adrien Mazarguil wrote: While debugging startup issues encountered with Clang (see "eal: fix undefined behavior in fbarray"), I noticed that fbarray stores indices, sizes and masks on signed integers involved in bitwise operations. Such operations almost invariably cause un

[dpdk-dev] [PATCH v3 2/2] eal: fix signed integers in fbarray

2018-04-13 Thread Adrien Mazarguil
While debugging startup issues encountered with Clang (see "eal: fix undefined behavior in fbarray"), I noticed that fbarray stores indices, sizes and masks on signed integers involved in bitwise operations. Such operations almost invariably cause undefined behavior with values that cannot be repr