On Wed, May 03, 2023 at 04:39:14PM +0100, Ferruh Yigit wrote: > On 5/3/2023 4:14 PM, Bruce Richardson wrote: > > Add a deprecation notice informing users that we will require a C11 > > compiler from 23.11 release onwards. This requirement was agreed by > > technical board to enable use of newer C language features, e.g. > > standard atomics. [1] > > > > [1] > > http://inbox.dpdk.org/dev/dbapr08mb58148cec3e1454e8848a938998...@dbapr08mb5814.eurprd08.prod.outlook.com/ > > > > Signed-off-by: Bruce Richardson <bruce.richard...@intel.com> > > --- > > doc/guides/rel_notes/deprecation.rst | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/doc/guides/rel_notes/deprecation.rst > > b/doc/guides/rel_notes/deprecation.rst > > index dcc1ca1696..9a391d2c49 100644 > > --- a/doc/guides/rel_notes/deprecation.rst > > +++ b/doc/guides/rel_notes/deprecation.rst > > @@ -11,6 +11,12 @@ here. > > Deprecation Notices > > ------------------- > > > > +* C Compiler: From DPDK 23.11 onwards, > > + building DPDK will require a C compiler which supports the C11 standard, > > or later. > > + Please note: > > + - C11 is supported from GCC version 5 onwards, and is the default > > language version in that release > > + - C11 is the default compilation mode in Clang from version 3.6 > > + > > * kvargs: The function ``rte_kvargs_process`` will get a new parameter > > for returning key match count. It will ease handling of no-match case. > > > > This only applies to DPDK internals, right? > Application linked with DPDK library won't have this requirement, > meaning DPDK public headers won't rely on C99 and C11 features. > > Although this is a deprecation notice for DPDK, if above is correct, > does it make sense to highlight it to not confuse users?
it applies to applications as well because dpdk exposes integers expected to be atomic via headers and inline functions use atomic functions both internal/external.
