Hi,
I'm working on the Hexagon SDK, version 3.3.2. I noticed that the flat profile cycle values for a function obtained using gprof are different from hexagon_sim_read_cycles. Can someone explain the difference?
Also, is hexagon_sim_read_cycles deprecated? There is no difference in the cycles computation using hexagon_sim_read_cycles, hexagon_sim_read_tcycles and hexagon_sim_read_pcycles. What tool is relevant for cycle computation?
BR,
Naveen
Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.
