On Thu, Jan 12, 2023 at 11:35:55AM +0000, Bruce Richardson wrote: > Traditionally, DPDK has never specified a minimum C standard used either > in DPDK builds or for applications using DPDK. Following discussion > on-list about C standards, this RFC attempts to start the process of > codifying what our standards expectations are. No code changes are made > by this RFC, instead only the build parameters are changed to explicitly > specify: > > * C99 standard is used to build DPDK itself. This is supported by all > supported compiler versions of GCC and Clang. > * The headers are checked for compatibility with gcc89 standard, which > was the default standard used by the oldest supported version of GCC. > DPDK headers do not build with the official C89 standard, and, to the > best of my knowledge, have never done so.
subject to the technical board meeting 2023/02/22 in relation to atomics and adoption of C11 starting in 23.11 does anything stop us from conditionally enabling/defaulting -std=C11 for all platforms immediately except for RHEL/CentOS 7? so long as we don't actually start using C11 features we should be able to do this? or would we be worried that C11 feature use would creep in? just curious. > > Bruce Richardson (1): > build: increase minimum C standard for DPDK builds > > buildtools/chkincs/meson.build | 1 + > meson.build | 1 + > 2 files changed, 2 insertions(+) > > -- > 2.37.2
