-
Notifications
You must be signed in to change notification settings - Fork 8.1k
treewide: Enforce C17 as the minimum required C standard #97076
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -35,16 +35,14 @@ toolchain that supports the C99 standard and above: | |
* variadic macros | ||
* ``restrict`` qualification | ||
|
||
Some Zephyr components make use of the features newly introduced in the 2011 | ||
release of the ISO C standard (ISO/IEC 9899:2011, hereinafter referred to as | ||
C11) such as the type-generic expressions using the ``_Generic`` keyword. For | ||
example, the :c:func:`cbprintf` component, used as the default formatted output | ||
processor for Zephyr, makes use of the C11 type-generic expressions, and this | ||
effectively requires most Zephyr applications to be compiled using a compiler | ||
toolchain that supports the C11 standard and above. | ||
Additionally, some modules and features make use of features introduced in the | ||
2017 version of the standard (ISO/IEC 9899:2017): | ||
|
||
* _Generic keyword | ||
* _Static_assert keyword | ||
|
||
In summary, it is recommended to use a compiler toolchain that supports at | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Rather than recommended, it seems mandatory now? Edit: please note that GitHub is not highlighting the right line for my comment. I mean the "In summary, it is recommended to use a compiler..." There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I think I will change this text as you suggest. Thanks. |
||
least the C11 standard for developing with Zephyr. It is, however, important to | ||
least the C17 standard for developing with Zephyr. It is, however, important to | ||
note that some optional Zephyr components and external modules may make use of | ||
the C language features that have been introduced in more recent versions of | ||
the standards, in which case it will be necessary to use a more up-to-date | ||
|
Uh oh!
There was an error while loading. Please reload this page.