 RealView Linker and Utilities Guide | |
| Home Products Events Support | |
On-Line Manuals
RealView Linker and Utilities Guide
Preface Introduction The Linker Command Syntax About armlink
Input to armlink Output from armlink Ordering command-line options Specifying command-line options with an environmen armlink command syntax Accessing help and information Project template options Specifying an input file list Controlling linker behavior Specifying the output type and the output filename Specifying memory map information for the image Controlling debug information Controlling image contents Controlling veneer generation Specifying Byte Addressing mode Generating image-related information Controlling linker diagnostics Using a via file Miscellaneous Using the Basic Linker Functionality Accessing Image Symbols Using Scatter-loading Description Files Using the ARM Librarian Using fromelfControlling linker diagnostics
  | |||
  |  | ||
| |||
| Home > The Linker Command Syntax > armlink command syntax > Controlling linker diagnostics | |||
These options control how the linker emits diagnostics:
‑‑diag_style arm|ide|gnuChange the formatting of warning and error messages.
‑‑diag_style armis the default,‑‑diag_style gnumatches the format reported by gcc, and‑‑diag_style idematches the format reported by Microsoft Visual Studio.‑‑diag_suppresstaglistDisables all diagnostic messages that have the specified tag(s).
This option requires a comma-separated list of diagnostic message numbers that specifies the messages that must be suppressed. For example, to suppress the warning messages that have numbers
L6314WandL6305W, use the following command:armlink ‑‑diag_suppress L6314,L6305 ...‑‑diag_warningtaglistSets diagnostic messages that have the specified tag(s) to be displayed as warning messages, for example, where you want to downgrade an error message.
This option requires a comma-separated list of diagnostic message numbers that specifies the messages that must be downgraded.
‑‑errorsfileRedirects the diagnostics from the standard error stream to
fileThe specified file is created at the start of the link stage. If a file of the same name already exists, it is cleared.
If
file‑‑listfileRedirects the diagnostics from output of the
‑‑info,‑‑map,‑‑symbols,--verbose,‑‑xref,‑‑xreffrom, and‑‑xreftocommands tofileThe specified file is created when diagnostics are output. If a file of the same name already exists, it is overwritten. However, if diagnostics are not output, a file is not created. In this case, the contents of any existing file with the same name remain unchanged.
If
file‑‑verbosePrints detailed information about the link operation, including the objects that are included and the libraries from which they are taken. Because this output is typically quite long, you might want to use this command with the
‑‑listcommand to redirect the information tofilefileUse
‑‑verboseto output diagnostics tostdout.
The RVCT tools automatically insert an identification letter to diagnostic messages, as described in Table 2.1. Using these prefix letters enables the RVCT tools to use overlapping message ranges.
Table 2.1. Identifying diagnostic messages
| Prefix letter | RVCT tool |
|---|---|
C | armcc |
A | armasm |
L | armlink or armar |
Q | fromelf |
The following rules apply:
All the RVCT tools act on a message number without a prefix.
A message number with a prefix is only acted on by the tool with the matching prefix.
A tool does not act on a message with a non matching prefix.
Thus, the linker prefix L can be used with ‑‑diag_error, ‑‑diag_remark, and ‑‑diag_warning, or when suppressing messages, for example:
armlink ‑‑diag_suppress L6314,L6305 ...
| Copyright © 2007 ARM Limited. All rights reserved. | ARM DUI 0377A |
 PDF version | |
| Home > The Linker Command Syntax > armlink command syntax > Controlling linker diagnostics | |
| |
| Contact Site Map Press Privacy | Copyright © 2008 Keil™, An ARM® Company. All rights reserved. |
