13.07.2015 Views

TASKING VX-toolset for ARM User Guide

TASKING VX-toolset for ARM User Guide

TASKING VX-toolset for ARM User Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

<strong>TASKING</strong> <strong>VX</strong>-<strong>toolset</strong> <strong>for</strong> <strong>ARM</strong> <strong>User</strong> <strong>Guide</strong>Environment1.1(R)All code shall con<strong>for</strong>m to ISO 9899:1990 "Programming languages - C", amendedand corrected by ISO/IEC 9899/COR1:1995, ISO/IEC 9899/AMD1:1995, and ISO/IEC9899/COR2:1996.1.2(R)No reliance shall be placed on undefined or unspecified behavior.x1.3(R)Multiple compilers and/or languages shall only be used if there is a common definedinterface standard <strong>for</strong> object code to which the languages/compilers/assemblerscon<strong>for</strong>m.x1.4(R)The compiler/linker shall be checked to ensure that 31 character significance andcase sensitivity are supported <strong>for</strong> external identifiers.x1.5(A)Floating-point implementations should comply with a defined floating-point standard.Language extensions2.12.22.32.4(R)(R)(R)(A)Assembly language shall be encapsulated and isolated.Source code shall only use /* ... */ style comments.The character sequence /* shall not be used within a comment.Sections of code should not be "commented out". In general, it is not possible todecide whether a piece of comment is C code that is commented out, or just somepseudo code. Instead, the following heuristics are used to detect possible C codeinside a comment: - a line ends with ';', or - a line starts with '}', possibly preceded bywhite spaceDocumentationx3.1(R)All usage of implementation-defined behavior shall be documented.x3.2(R)The character set and the corresponding encoding shall be documented.x3.3(A)The implementation of integer division in the chosen compiler should be determined,documented and taken into account.3.4(R)All uses of the #pragma directive shall be documented and explained. This rule isreally a documentation issue. The compiler will flag all #pragma directives asviolations.3.5(R)The implementation-defined behavior and packing of bit-fields shall be documentedif being relied upon.x3.6(R)All libraries used in production code shall be written to comply with the provisions ofthis document, and shall have been subject to appropriate validation.Character sets4.14.2(R)(R)Only those escape sequences that are defined in the ISO C standard shall be used.Trigraphs shall not be used.868

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

Saved successfully!

Ooh no, something went wrong!