summaryrefslogtreecommitdiffstats
path: root/spec/rtems/basedefs/req/no-return-0.yml
diff options
context:
space:
mode:
Diffstat (limited to 'spec/rtems/basedefs/req/no-return-0.yml')
-rw-r--r--spec/rtems/basedefs/req/no-return-0.yml24
1 files changed, 24 insertions, 0 deletions
diff --git a/spec/rtems/basedefs/req/no-return-0.yml b/spec/rtems/basedefs/req/no-return-0.yml
new file mode 100644
index 00000000..7643ef51
--- /dev/null
+++ b/spec/rtems/basedefs/req/no-return-0.yml
@@ -0,0 +1,24 @@
+SPDX-License-Identifier: CC-BY-SA-4.0
+copyrights:
+- Copyright (C) 2020 embedded brains GmbH (http://www.embedded-brains.de)
+enabled-by: true
+links:
+- role: requirement-refinement
+ uid: ../if/no-return
+non-functional-type: interface
+rationale: |
+ The GNU C compiler can optimize such a function without regard to what would
+ happen if it ever did return. Declaring a function ${../if/no-return:/name}
+ also avoids spurious warnings of uninitialized variables.
+references: []
+requirement-type: non-functional
+text: |
+ When the code is compiled with the GNU C compiler starting at version 2.5
+ or the ``__cplusplus`` symbol is defined with version ``201103L`` or higher
+ or the ``__STDC_VERSION__`` symbol is defined with version ``201112L``
+ or higher,
+ and the ${../if/no-return:/name} macro is used as first part of a
+ function declaration or definition,
+ the ${../if/no-return:/name} macro shall
+ inform the compiler that this function does not return when called.
+type: requirement