RealView Compilation Tools - ARM Information Center

Compiler Command-line Options
Errors
When --strict_warnings is in force and a violation of the relevant ISO standard occurs,
the compiler normally issues a warning message.
The severity of diagnostic messages can be controlled in the usual way.
Note
In some cases, the compiler issues an error message instead of a warning when it detects
something that is strictly illegal, and terminates the compilation. For example:
#ifdef $Super$
extern void $Super$$__aeabi_idiv0(void); /* intercept __aeabi_idiv0 */
#endif
Compiling this code with --strict_warnings generates an error if you do not use the
--dollar option.
Example
void foo(void)
{
long long i; /* okay in nonstrict C90 */
}
Compiling this code with --strict_warnings generates a warning message.
Compilation continues, even though the expression long long is strictly illegal.
See also
• Source language modes on page 1-3
• Dollar signs in identifiers on page 3-13
• --c90 on page 2-22
• --c99 on page 2-22
• --cpp on page 2-30
• --gnu on page 2-67
• --strict, --no_strict on page 2-119.
2.1.154 --sys_include
This option removes the current place from the include search path.
ARM DUI 0348C Copyright © 2007-2010 ARM. All rights reserved. 2-121
ID101213
Non-Confidential,