summaryrefslogtreecommitdiffstats
path: root/spec/rtems/basedefs/req/inline-routine-0.yml
blob: 6181a1002b41791b1de39b96ab05af5bd601245f (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
SPDX-License-Identifier: CC-BY-SA-4.0
copyrights:
- Copyright (C) 2020 embedded brains GmbH & Co. KG
enabled-by: true
functional-type: function
links:
- role: interface-function
  uid: ../if/inline-routine
rationale: |
  ``inline`` and ``__inline__`` have the same effect at least for the
  GNU C compiler. ``__inline__`` works even if the GNU C compiler
  is invoked with the ``-ansi``, or ``-std`` flags.

  The compiler may still emit code for a function defined or declared
  with ``static inline`` or ``static __inline__``. Therefore,
  if you want to put an inline function definition into a header
  file, consider ``extern inline`` instead (see the compiler
  documentation).
references: []
requirement-type: functional
text: |
  The ${../if/inline-routine:/name} macro shall evaluate
  to the keywords ``static inline`` or ``static __inline__``
  which ever variant is available to the used compiler.
type: requirement