Specifications

Error Message Meaning and Remedy
Reasons
1. The executable file may be invalid. It may be
damaged or contain a program for another member
of the Renesas H8 processor family with an
extended instruction set.
2. The entry address specified for the current
subprogram may be invalid; it may point to data
rather than code, or to code that is not loaded
directly from the executable file but is created or
copied here at run time.
3. The control-flow analysis may be exploring an
impossible path. Perhaps a dynamic jump was
misanalysed; perhaps the maximum value of a
switch/case index was overestimated.
Solution
Ensure that the executable file is correct and valid for
the H8/300. Analyse only code that exists in the
executable memory image at load time. Check the
analysis of dynamic jumps.
Jump via dynamic vector taken as return
Problem
The program contains a memory-indirect dynamic
jump instruction of the type JMP @@aa:8 that Bound-T
cannot resolve. See section 5.6. Bound-T treats this
instruction as if it were a return instruction.
Reasons
The programmer or compiler generated this
instruction for some reason.
Solution
Try to modify the program to avoid this instruction. If
a dynamic jump of this kind is necessary, determine
the possible jump destinations, analyse them with
Bound-T as separate subprograms, and add their
WCET bound to the WCET bound for the (truncated)
subprogram that contains the dynamic jump.
Jump via register taken as return
Problem
The program contains a register-indirect dynamic
jump instruction of the type JMP @Rn that does not
seem to use an address table. See section 5.6. Bound-T
treats this instruction as if it were a return instruction.
Reasons
The programmer or compiler generated this
instruction for some reason. Perhaps it is a C program
that uses function pointers.
Solution
Try to modify the program to avoid this instruction. If
a dynamic jump of this kind is necessary, determine
the possible jump destinations, analyse them with
Bound-T as separate subprograms, and add their
WCET bound to the WCET bound for the (truncated)
subprogram that contains the dynamic jump.
Line numbers unknown for this
subprogram
Problem
The COFF file defines no "first source line number" for
the present subprogram.
Reasons
Perhaps the subprogram was compiled without
debugging information.
Solution
Recompile with debugging information.
Line too long (over maximum characters)
in the extra-symbols file
Problem
The additional symbol-table file named in a -sym
command-line option contains a line that is longer
than the maximum length that Bound-T supports.
42 Error messages Bound-T for H8/300