Sergey A. Borshch schrieb:
Problem #1:
/ me hasn't a good idea either
Problem #2:
/me agrees with Oleg
Problem #3:
MSP430, MSP430X(241x, 26x, 46xx) and MSP430X2(5xxx) cores have different
instruction timings. Timings are calculated during disassembling (file
opcodes/msp430-dis.c, but calculated value not used in main disassembling
function print_insn_msp430(). Does we need instruction cycles information in
listings (so, we must fix comments output in print_insn_msp430) or not (so, we
can remove timing calculations from underlaying functions)?
knowing instruction timing is interesting to know at times. however it's
not a requirement to have the binutils doing this.
i'm usually creating the listings by msp430-objdump -dSt $^ >$@ on the
elf file as i want to see the absolute addresses. but i dont see the
cycle count there anyway.
chris
