On Fri, Oct 16, 2020 at 8:04 AM Honnappa Nagarahalli
wrote:
>
> When RTE_MAX_LCORE value is small, following compiler errors
> are observed.
>
> ../app/test/test_rcu_qsbr.c:296:54: error: iteration 2 invokes
> undefined behavior [-Werror=aggressive-loop-optimizations]
>
> ../app/test/test_rcu_qsbr
Hi Honnappa,
If setting value lower than 2 makes no sense as there is no place for
worker thread, then the patch is perfectly fine
>>> When RTE_MAX_LCORE value is small, following compiler errors are
>>> observed.
>>>
>>> ../app/test/test_rcu_qsbr.c:296:54: error: iteration 2 invokes
>>> unde
Hi Lukasz,
>
> Hi Honnappa,
>
> I verified building and testing and all the warnings/errors disappear for
> RTE_MAX_LCORE >= 2 and tests pass.
Thank you for testing this.
>
> I wonder, if it is possible to set RTE_MAX_LCORE = 1 ?
I thought, we would need 2 cores minimum, one for main and the
Hi Honnappa,
I verified building and testing and all the warnings/errors disappear
for RTE_MAX_LCORE >= 2 and tests pass.
I wonder, if it is possible to set RTE_MAX_LCORE = 1 ?
In such case there are still few places with array bounds exceedings:
Compiling C object 'app/test/3062f5d@@dpdk-test@e
When RTE_MAX_LCORE value is small, following compiler errors
are observed.
../app/test/test_rcu_qsbr.c:296:54: error: iteration 2 invokes
undefined behavior [-Werror=aggressive-loop-optimizations]
../app/test/test_rcu_qsbr.c:315:55: error: array subscript is above
array bounds [-Werror=array-boun
5 matches
Mail list logo
