Разработка, производство и продажа радиоэлектронной аппаратуры
|
Требуется программист в Зеленограде - обработка данных с датчиков; ColdFire; 40 тыс.
e-mail: jobsmp@pochta.ru
|
из доки, которая лежит в папке IAR [+]
Отправлено
MegaJohn 11 февраля 2008 г. 23:10
В ответ на:
Ответ (+) отправлено
Kukaracha 11 февраля 2008 г. 22:58
RANGE ERRORS
Some instructions do not work unless a certain condition holds after linking, for
example, that a branch target must be within a certain distance or that an address must
be even. The compiler or assembler generates tests and XLINK verifies that the
conditions hold when the files are linked. If a condition is not satisfied, XLINK
generates a range error or warning and prints a description of the error.
Example
Error[e18]: Range error, chip’s branch target is out of range
Where $ = vectorSubtraction + 0xC [0x804C]
in module "vectorRoutines" (vectorRoutines.r99),
offset 0xC in segment part 5, segment NEARFUNC_A
What: vectorNormalization - ($ + 8) [0x866B3FC]
Allowed range: 0xFDFFFFFC - 0x2000000
Operand: vectorNormalization [0x8673450]
in module VectorNorm (vectorNormalization.r99),
Offset 0x0 in segment part 0, segment NEARFUNC_V
Error[e18]: Range error
The first section is often the most important. The text after Range error is generated
by the compiler and describes of what is being tested. In this case XLINK tests if the
target of a branch instruction is in range.
Составить ответ | Вернуться на конференцию
Ответы