|Home > Linking Models Supported by armlink > Base Platform linking model|
Enables you to create dynamically linkable images that do not have the memory map enforced by the Base Platform Application Binary Interface (BPABI) linking model.
The Base Platform linking model enables you to:
To link with the Base Platform model, use the
If you specify this option, the linker acts as if you specified
with the following exceptions:
--scatter. If you do not specify
--scatter, then the standard BPABI memory model scatter file is used.
The following options are available:
The default value of the
--pltgot option is different to that for
--base_platform, the default is
--bpabithe default is
Each load region containing code might require a Procedure
Linkage Table (PLT) section to indirect calls from the load region to functions
where the address is not known at static link time. The PLT section for a load region
LR must be placed in
LR and be accessible at all times to code within
If you do not use a scatter file, the linker can ensure that the PLT section is placed correctly, and contains entries for calls only to imported symbols. If you specify a scatter file, the linker might not be able to find a suitable location to place the PLT.
To ensure calls between relocated load regions use a PLT entry:
--pltgot=directoption to turn on PLT generation.
--pltgot_opts=crosslroption to add entries in the PLT for calls from and to
RELOCload regions. The linker generates a PLT for each load region so that calls do not have to be extended to reach a distant PLT.
Be aware of the following: