Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What does the call graph in the map file mean?

file Graph map mean
0
Posted

What does the call graph in the map file mean?

0
0

> I can not find any explanation in the manual on the call graph section > of the map file generated by the linker. > – Some functions are marked with a star. These are functions on the critical path – i.e. if you want to reduce the amount of RAM used for arguments and locals, you can ignore those functions NOT marked with a star, because they do not influence the total. Of course if you change a critical function, and reduce the RAM needed, other functions may then become critical. > – “size #,#”. I guess it has something to do with arguments. The first number is the number of bytes of locals, and the second is the number of bytes of arguments. > – “offset #”. This is the offset at which this function’s RAM allocation starts. The offset is from the base of the local RAM block, which you will see in the COMMON section of the link map, after the file listing. > – INDIRECT ####. This represents all those functions called indirectly with a signature of ####. Since it is based on signature

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123