RealView Compilation Tools - ARM Information Center

Compiler Command-line Options
Note
When building a System V or ARM Linux shared library, use
--apcs /fpic together with --no_hide_all.
Restrictions
There are restrictions when you compile code with /ropi, or /rwpi, or /fpic.
/ropi
/rwpi
The main restrictions when compiling with /ropi are:
• The use of --apcs=/ropi is not supported when compiling C++.
• Some constructs that are legal C do not work when compiled for
--apcs=/ropi. For example:
extern const int ci; // ro
const int *p2 = &ci; // this static initialization
// does not work with --apcs=/ropi
To enable such static initializations to work, compile your code
using the --lower_ropi option. For example:
armcc --apcs=/ropi --lower_ropi
The main restrictions when compiling with /rwpi are:
• Some constructs that are legal C do not work when compiled for
--apcs=/rwpi. For example:
int i;
// rw
int *p1 = &i; // this static initialization
// does not work with --apcs=/rwpi
// --no_lower_rwpi
To enable such static initializations to work, compile your code
using the --lower_rwpi option. For example:
armcc --apcs=/rwpi
Note
You do not have to specify --lower_rwpi, because this is the default.
/fpic
The main restrictions when compiling with /fpic are:
• If you use --apcs=/fpic, the compiler exports only functions and
data marked __declspec(dllexport).
• If you use --apcs=/fpic and --no_hide_all on the same command
line, the compiler uses default ELF dynamic visibility for all
extern variables and functions that do not use __declspec(dll*).
The compiler disables auto-inlining for functions with default ELF
visibility.
ARM DUI 0348C Copyright © 2007-2010 ARM. All rights reserved. 2-7
ID101213
Non-Confidential,