29.10.2014 Views

ARM Compiler toolchain v4.1 for µVision Using the Compiler

ARM Compiler toolchain v4.1 for µVision Using the Compiler

ARM Compiler toolchain v4.1 for µVision Using the Compiler

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>Compiler</strong> Diagnostic Messages<br />

6.4 Prefix letters in compiler diagnostic messages<br />

The compilation tools automatically insert an identification letter to diagnostic messages. See<br />

Table 6-2. <strong>Using</strong> <strong>the</strong>se prefix letters enables <strong>the</strong> tools to use overlapping message ranges.<br />

Table 6-2 Identifying diagnostic messages<br />

Prefix letter<br />

C<br />

A<br />

L<br />

Q<br />

Tool<br />

armcc<br />

armasm<br />

armlink or armar<br />

fromelf<br />

The following rules apply:<br />

• All of <strong>the</strong> compilation tools act on a message number without a prefix.<br />

• A message number with a prefix is only acted on by <strong>the</strong> tool with <strong>the</strong> matching prefix.<br />

• A tool does not act on a message with a non-matching prefix.<br />

There<strong>for</strong>e, <strong>the</strong> compiler prefix C can be used with --diag_error, --diag_remark, and<br />

--diag_warning, or when suppressing messages, <strong>for</strong> example:<br />

armcc --diag_suppress=C1287,C3017 ...<br />

Use <strong>the</strong> prefix letters to control options that are passed from <strong>the</strong> compiler to o<strong>the</strong>r tools, <strong>for</strong><br />

example, include <strong>the</strong> prefix letter L to specify linker message numbers.<br />

6.4.1 See also<br />

Concepts<br />

• <strong>Compiler</strong> diagnostics on page 6-2.<br />

<strong>ARM</strong> DUI 0375C Copyright © 2007-2008, 2011 <strong>ARM</strong>. All rights reserved. 6-5<br />

ID061811<br />

Non-Confidential

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

Saved successfully!

Ooh no, something went wrong!