Texas Instruments TMS320C6000 Programmer's Manual page 119

4.1.1.1 Far Function Cells
4.1.1.2 Far Global Data
In this case, the call to the function atoi is too far away from the location where
this code is linked.
It is possible that use of –s will cause instructions to move around some and
thus the instruction at the given SPC offset is not what you expect. The branch
or MVK nearest to that instruction is the most likely cause. Or, you can rebuild
the whole application with –s –al and relink to see the new SPC offset of the
error.
If you are tracing a problem in a hand-coded assembly file, the process is simi-
lar, but you merely re-assemble with the –l option instead of recompiling.
To fix a branch problem, your choices are:
Use the –mr1 option to force the call to atoi, and all other RTS functions,
to be far.
Compile with –ml1 or higher to force all calls to be far.
Rewrite your linker command file (looking at a map file usually helps) so
that all the calls to atoi are close (within 0x100000 words) to where atoi is
linked.
If the problem instruction is an MVK, then you need to understand why the
constant expression does not fit.
For C code, you might find the instruction looks like:
50 000000a4 0200002A%
In this case, the address of the C object ary is being computed as if ary is de-
clared near (the default), but because it falls outside of the 15-bit address
range the compiler presumes for near objects, you get the warning. To fix this
problem, you can declare ary to be far, or you can use the correct cl6x –ml n
memory model option to automatically declare ary and other such data objects
to be far. See chapter 2 of the TMS320C6000 Optimizing C/C++ Compiler
User's Guide for more information on –ml n .
It is also possible that ary is defined as far in one file and declared as near in
this file. In that case, insure ary is defined and declared consistently to all files
in the project.
How to Use Linker Error Messages
MVK (_ary–$bss),B4
Linking Issues
; |5|
4-3