04.01.2015 Views

RealView Compilation Tools - ARM Information Center

RealView Compilation Tools - ARM Information Center

RealView Compilation Tools - ARM Information Center

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Compiler Command-line Options<br />

Usage<br />

--strict enforces compliance with:<br />

ISO C90 • ISO/IEC 9899:1990, the 1990 International Standard for C.<br />

• ISO/IEC 9899 AM1, the 1995 Normative Addendum 1.<br />

ISO C99 ISO/IEC 9899:1999, the 1999 International Standard for C.<br />

ISO C++<br />

ISO/IEC 14822:2003, the 2003 International Standard for C++.<br />

Errors<br />

When --strict is in force and a violation of the relevant ISO standard occurs, the<br />

compiler issues an error message.<br />

The severity of diagnostic messages can be controlled in the usual way.<br />

Example<br />

void foo(void)<br />

{<br />

long long i; /* okay in nonstrict C90 */<br />

}<br />

Compiling this code with --strict generates an error.<br />

See also<br />

• --c90 on page 2-22<br />

• --c99 on page 2-22<br />

• --cpp on page 2-30<br />

• --gnu on page 2-67<br />

• --strict_warnings<br />

• Dollar signs in identifiers on page 3-13<br />

• Source language modes on page 1-4 in the Compiler User Guide.<br />

2.1.153 --strict_warnings<br />

Diagnostics that are errors in --strict mode are downgraded to warnings, where<br />

possible. It is sometimes not possible for the compiler to downgrade a strict error, for<br />

example, where it cannot construct a legitimate program to recover.<br />

2-120 Copyright © 2007-2010 <strong>ARM</strong>. All rights reserved. <strong>ARM</strong> DUI 0348C<br />

Non-Confidential,<br />

ID101213

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!