Re: [dpdk-dev] [PATCH v2] lib/rcu: avoid literal suffix warning in C++ mode

2020-10-05 Thread Thomas Monjalon
> > Sequences like "value = %"PRIu64 (no space before PRIu64) are parsed as a > > single preprocessor token, user-defined-string-literal, in C++11 onwards. > > While modern compilers are smart enough to parse this properly, GCC 9.3.0 > > generates warnings like: > > > > rte_rcu_qsbr.h:555:26:

Re: [dpdk-dev] [PATCH v2] lib/rcu: avoid literal suffix warning in C++ mode

2020-09-04 Thread Honnappa Nagarahalli
> > Sequences like "value = %"PRIu64 (no space before PRIu64) are parsed as a > single preprocessor token, user-defined-string-literal, in C++11 onwards. > While modern compilers are smart enough to parse this properly, GCC 9.3.0 > generates warnings like: > > rte_rcu_qsbr.h:555:26: warning

[dpdk-dev] [PATCH v2] lib/rcu: avoid literal suffix warning in C++ mode

2020-09-04 Thread Dmitry Kozlyuk
Sequences like "value = %"PRIu64 (no space before PRIu64) are parsed as a single preprocessor token, user-defined-string-literal, in C++11 onwards. While modern compilers are smart enough to parse this properly, GCC 9.3.0 generates warnings like: rte_rcu_qsbr.h:555:26: warning: invalid suffix