Hi all.I have started playing with Amplifier XE yesterday and have hit a few issues questions that I might need help with. My experience with Amplifier is limited as most profiling work in the past has been done with Vtune...1) When looking at the profile data for a basic hotspot capture, all synchronization calls appear to count as busy CPU time so a large portion of time on some threads appear with WaitForObject at the top. Is there a way to exclude this or at least make sure only the real busy CPU time is reported for cases like these. Or at least some what to know which portion of this time was actually active versus the thread being asleep.2) I have been noticing someinconsistenciesin the reporting between the bottom-up and top-down trees. In bottom up, one top function may show as a mid-level function which calls other functions (which are not inlined). Looking at the code/assembly view shows that most of the time is spent in some of the sub-functions called but are not reported. However, if I drill down the top-down tree, the sub-functions seem to be represented accurately.3) In regards to API. The beta invite indicates an API can be used to mark frames to be used in the profile data. I would assume this is the ittnotify API? But in another non beta related article for Amplifier, it seems to imply the API calls supported are Pause/Resume/Mark. Is there some decent documentation somewhere as to which API calls can be used, how to use them and how they will affect the results in Amplifier XE?Thanks,Sebastien St-LaurentNeversoft Entertainment LLC
For more complete information about compiler optimizations, see our Optimization Notice.