For example, looking at the 'firmware.dis' file of a MicroPython built for a Pico ...It's not just that one label, and it's even worse with my own build of MicroPython ...I guess the first question is why or how ?
And secondly how to know which is being called by other routines in that file, to which the answer may be that I can't rely solely on the label name, but have to try and work out what address is actually being referenced ?
Code:
pi@Pi3B:~/pico/micropython/ports/rp2/build $ grep "mp_hal_ticks_ms>:" firmware.dis1001b8e0 <mp_hal_ticks_ms>:1001ff64 <mp_hal_ticks_ms>:Code:
pi@Pi3B:~/pico/micropython/ports/picopython/build $ grep "mp_hal_ticks_ms>:" picopython.dis1001d214 <mp_hal_ticks_ms>:1001f900 <mp_hal_ticks_ms>:100237f8 <mp_hal_ticks_ms>:10024fac <mp_hal_ticks_ms>:10025550 <mp_hal_ticks_ms>:1002cf68 <mp_hal_ticks_ms>:10031122 <mp_hal_ticks_ms>:10032d64 <mp_hal_ticks_ms>:10049c50 <mp_hal_ticks_ms>:And secondly how to know which is being called by other routines in that file, to which the answer may be that I can't rely solely on the label name, but have to try and work out what address is actually being referenced ?
Statistics: Posted by hippy — Fri Jan 26, 2024 3:42 pm
