Hi,
Intel v-tune cannot seem to resolve the function source code.
I get something like this;
fucntion_hot_spot() xxxx ms
but it does not expand on this.
Issues With V-Tune not resolving source properly.
пт, 13/07/2012 - 12:02
Issues With V-Tune not resolving source properly.
Пожалуйста, обратитесь к странице Уведомление об оптимизации для более подробной информации относительно производительности и оптимизации в программных продуктах компании Intel.
- Войдите, чтобы оставлять комментарии
сб, 14/07/2012 - 05:51
I can't see your screen shot and I suppose that you have to check - if you built your binary with symbol info.
Secondary, if you already have symbol info - regarding that you said "function_hot_spots() xxx ms" - probably you haveset your source search directories in project properties (ifsource file is located at different directory of binary), and do Re-resolving on existing result.
Good luck.
Regards, Peter
- Войдите, чтобы оставлять комментарии
сб, 14/07/2012 - 10:33
Hi,
I have made sure that the /Zi and /DEBUG are specified. It does not matter what analysis I use, always the same result.
Here is a shot
- Войдите, чтобы оставлять комментарии
вс, 15/07/2012 - 04:23
I guess that you want to know hot line(s) in DVQuantizer::encodeBlock() BecauseDVQuantizer::encodeBlock is called in deep loop, it might be compiled by inlined function if you specified optmization options. It means CPU time ofDVQuantizer::encodeBlock wat counted in functionDVQuantizer::encode(). If you use Intel C++ compiler, please read this article to solve this problem. Otherwise, you can use assembly view, to find associated (hot) instructions inDVQuantizer::encodeBlock Thanks, Peter
- Войдите, чтобы оставлять комментарии
вс, 15/07/2012 - 06:41
Thanks, following that article resolved my issues.