 RealView Compiler User's Guide | |
| Home Products Events Support | |
On-Line Manuals
RealView Compiler User's Guide
Preface Introduction Getting started with the ARM Compiler Using command-line options
Invoking the ARM compiler Ordering command-line options Specifying command-line options with an environmen Autocompleting command-line options Reading compiler options from a file Specifying keyboard input File naming conventions Portability Output files Include files The current place The RVCT31INC environment variable The search path The TMP and TMPDIR environment variables Precompiled header files Automatic PCH processing Manual PCH processing Controlling the output of messages during PCH proc Performance issues Specifying the procedure call standard (AAPCS) Interworking qualifiers Position independence qualifiers Using linker feedback Thread-local storage Eight‑byte alignment features Compiler Features Coding Practices Diagnostic Messages Using the Inline and Embedded Assemblers SemihostingInvoking the ARM compiler
  | |||
  |  | ||
| |||
| Home > Getting started with the ARM Compiler > Using command-line options > Invoking the ARM compiler | |||
The command for invoking the ARM compiler is:
armcc [help‑options] [source‑language] [search‑paths] [project-template-options] [PCH‑options] [preprocessor‑options] [C++‑language] [output‑format] [target‑options] [debug‑options] [code‑generation‑options] [optimization‑options] [diagnostic‑options] [additional‑checks] [PCS‑options] [pass‑thru‑options] source
See Chapter 2 Compiler Command-line Options in the Compiler Reference Guide for more information on each of the following options:
help‑optionsShows the main command-line options, the version number of the compiler and how the compiler has processed the command line:
source‑languageSpecifies the source language variants accepted by the compiler:
These language options can be combined. For example:
armcc ‑‑c90 ‑‑gnusearch‑pathsSpecifies the directories to search for included files:
See Include files for more information on how these options work together.
project-template-optionsControls the behavior of project templates:
PCH‑optionsControls the processing of PCH files:
preprocessor‑optionsSpecifies preprocessor behavior, including preprocessor output and macro definitions:
C++‑languageSpecifies options specific to C++ compilation:
output‑formatSpecifies the format for the compiler output. You can use these options to generate object files, assembly language output listing files, and make file dependency files:
target‑optionsSpecifies the target processor or architecture and the target instruction set in use at startup:
See Selecting the target device for more information.
debug‑optionsControls the format and generation of debug tables:
code‑generation‑optionsSpecifies the code generation options for the ARM compiler, including endianness, symbol visibility, and alignment criteria:
optimization‑optionsControls the level and type of code optimization:
Note
Optimization criteria can limit the debug information generated by the compiler.
diagnostic‑optionsControls the diagnostic messages output by the compiler:
See Chapter 5 Diagnostic Messages for more information.
multiple compilationsSpecifies the feedback file that contains information about a previous build:
PCS‑optionsSpecifies the procedure call standard to use:
See Specifying the procedure call standard (AAPCS) for more information.
pass‑thru‑optionsInstructs the compiler to pass options to other RVCT tools:
sourceProvides the filenames of one or more text files containing C or C++ source code. By default, the compiler looks for source files, and creates output files, in the current directory.
If a source file is an assembly file, that is, one with an extension of
.s, the compiler activates the ARM assembler to process the source file.
The ARM compiler accepts one or more input files, for example:
armcc ‑c [options]ifile_1...ifile_n
Specifying a dash ‑ for an input file causes the compiler to read from stdin. To specify that all subsequent arguments are treated as filenames, not as command switches, use the POSIX option ‑‑. See Using command-line options for more information.
The compiler startup configuration is determined by the compiler according to the specified command‑line options and the filename extensions. Command‑line options override the default configuration determined by the filename extension. The compiler startup language can be C or C++ and the instruction set can be ARM or Thumb. You can also specify the startup instruction set by using the ‑‑arm or ‑‑thumb option.
When you compile multiple files with a single command, all files must be of the same type, either C or C++. The compiler cannot switch the language based on the file extension. The following example produces an error, because the specified source files have different languages:
armcc ‑c test1.c test2.cpp
If you specify files with conflicting file extensions you can force the compiler to compile either for C or for C++, regardless of file extension. For example:
armcc ‑c ‑‑cpp test1.c test2.cpp
Where an unrecognized extension begins with .c, for example, filename.cmd
Support for processing PreCompiled Header (PCH) files is not available when you specify multiple source files in a single compilation. If you request PCH processing and specify more than one primary source file, the compiler issues an error message, and aborts the compilation.
See Precompiled header files for more information.
| Copyright © 2007 ARM Limited. All rights reserved. | ARM DUI 0375A |
 PDF version | |
| Home > Getting started with the ARM Compiler > Using command-line options > Invoking the ARM compiler | |
| |
| Contact Site Map Press Privacy | Copyright © 2008 Keil™, An ARM® Company. All rights reserved. |
