The character set (5.1.1.2)
The source character set is the same as the physical source file multibyte character set. By default, the standard ASCII character set is used. However, it can be UTF-8, UTF-16, or the system locale. See Text encodings.
Main (5.1.2.1)
The function called at program startup is called main. No prototype is declared for main, and the only definition supported for main is:
int main(void)
To change this behavior, see System initialization.
The effect of program termination (5.1.2.1)
Terminating the application returns the execution to the startup code (just after the call to main).
Alternative ways to define main (5.1.2.2.1)
There is no alternative ways to define the main function.
The argv argument to main (5.1.2.2.1)
The argv argument is not supported.
Streams as interactive devices (5.1.2.3)
The streams stdin, stdout, and stderr are treated as interactive devices.
Multithreaded environment (5.1.2.4)
By default, the IAR runtime environment does not support more than one thread of execution. With an optional third-party RTOS, it might support several threads of execution.
Signals, their semantics, and the default handling (7.14)
In the DLIB runtime environment, the set of supported signals is the same as in Standard C. A raised signal will do nothing, unless the signal function is customized to fit the application.
Signal values for computational exceptions (7.14.1.1)
In the DLIB runtime environment, there are no implementation-defined values that correspond to a computational exception.
Signals at system startup (7.14.1.1)
In the DLIB runtime environment, there are no implementation-defined signals that are executed at system startup.
Environment names (7.22.4.6)
In the DLIB runtime environment, there are no implementation-defined environment names that are used by the getenv function.
The system function (7.22.4.8)
The system function is not supported.