|
||
| Products Download Events Support Videos | ||
Technical Support
On-Line Manuals
Compiler User Guide
Preface
Overview of the Compiler
Getting Started with the Compiler
Compiler Features
Compiler Coding Practices
The compiler as an optimizing compiler
Compiler optimization for code size versus speed
Compiler optimization levels and the debug view
Selecting the target processor at compile time
Enabling FPU for bare-metal
Optimization of loop termination in C code
Loop unrolling in C code
Compiler optimization and the volatile keyword
Code metrics
Code metrics for measurement of code size and data
Stack use in C and C++
Benefits of reducing debug information in objects
Methods of reducing debug information in objects a
Guarding against multiple inclusion of header file
Methods of minimizing function parameter passing o
Returning structures from functions through regist
Functions that return the same result when called
Comparison of pure and impure functions
Recommendation of postfix syntax when qualifying f
Inline functions
Compiler decisions on function inlining
Automatic function inlining and static functions
Inline functions and removal of unused out-of-line
Automatic function inlining and multifile compilat
Restriction on overriding compiler decisions about
Compiler modes and inline functions
Inline functions in C++ and C90 mode
Inline functions in C99 mode
Inline functions and debugging
Types of data alignment
Advantages of natural data alignment
Compiler storage of data objects by natural byte a
Relevance of natural data alignment at compile tim
Unaligned data access in C and C++ code
The __packed qualifier and unaligned data access i
Unaligned fields in structures
Performance penalty associated with marking whole
Unaligned pointers in C and C++ code
Unaligned Load Register (LDR) instructions generat
Comparisons of an unpacked struct, a __packed stru
Compiler support for floating-point arithmetic
Default selection of hardware or software floating
Example of hardware and software support differenc
Vector Floating-Point (VFP) architectures
Limitations on hardware handling of floating-point
Implementation of Vector Floating-Point (VFP) supp
Compiler and library support for half-precision fl
Half-precision floating-point number format
Compiler support for floating-point computations a
Types of floating-point linkage
Compiler options for floating-point linkage and co
Floating-point linkage and computational requireme
Processors and their implicit Floating-Point Units
Integer division-by-zero errors in C code
Software floating-point division-by-zero errors in
About trapping software floating-point division-by
Identification of software floating-point division
Software floating-point division-by-zero debugging
New language features of C99
New library features of C99
// comments in C99 and C90
Compound literals in C99
Designated initializers in C99
Hexadecimal floating-point numbers in C99
Flexible array members in C99
__func__ predefined identifier in C99
inline functions in C99
long long data type in C99 and C90
Macros with a variable number of arguments in C99
Mixed declarations and statements in C99
New block scopes for selection and iteration state
_Pragma preprocessing operator in C99
Restricted pointers in C99
Additional Complex numbers in C99
Boolean type and Extended integer types and functions in How to prevent uninitialized data from being initi
Compiler Diagnostic Messages
Using the Inline and Embedded Assemblers of the AR
Compiler Command-line Options
Language Extensions
Compiler-specific Features
C and C++ Implementation Details
What is Semihosting?
Via File Syntax
Summary Table of GNU Language Extensions
Standard C Implementation Definition
Standard C++ Implementation Definition
C and C++ Compiler Implementation Limits
Compiler optimization for code size versus speed
| Non-Confidential |  PDF version | ARM DUI0375H | ||
| ||||
| Home > Compiler Coding Practices > Compiler optimization for code size versus speed | ||||
4.2 Compiler optimization for code size versus speed
The compiler can optimize for either code size or performance.
The following options control whether the compiler optimizes for code
size or performance:
-Ospace- This option causes the compiler to optimize mainly for code size. This is the default option.
-Otime- This option causes the compiler to optimize mainly for speed.
For best results, you must build your application using the
most appropriate command-line option.
Note
These command-line options instruct the compiler to use optimizations
that deliver the effect wanted in the vast majority of cases. However,
it is not guaranteed that
-Otime always generates faster
code, or that -Ospace always generates smaller
code.| Non-Confidential | PDF version | ARM DUI0375H |
| Copyright © 2007, 2008, 2011, 2012, 2014-2016 ARM. All rights reserved. |
| Home > Compiler Coding Practices > Compiler optimization for code size versus speed |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Contact |
 |
||||