- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am executing performance analysis of C++ image processing code through VTune of Parallel Studio XE 2015 Composer Edition on Windows 7 and Intel Core i5 2400 processor platform, but could not able to see complete list of functions into VTune report. What could be the correct way to see all the written function in VTune report ?
FYR, Intel Compilers settings are
/Zi /nologo /W3 /WX- /Ox /Oi /Ot /GL /D "NDEBUG" /D "_CONSOLE" /D "_UNICODE" /D "UNICODE" /Gm- /EHsc /MD /GS /Gy /fp:precise /Zc:wchar_t /Zc:forScope /Fp"x64\Release\ExeName.pch" /Fa"x64\Release\" /Fo"x64\Release\" /Fd"x64\Release\vc100.pdb" /Gd /errorReport:queue
Regards,
Tejas
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In order to retain function name symbols across in-lining, there is the option -debug:inline-debug-info
Still, you will not see functions for which there are insufficient samples. On a sampling run of less than 20 seconds, you will need to increase sampling rate.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would adjust @Tim Prince's to cosmetic change, since it is on Windows, it is /Qinline-debug-info
but I'd like to place another question, does this option work also on large preprocessor macros?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Though, I get with ICC 14.0 with latest updates:
1>icl: : message #10010: option '/Qinline-debug-info' is deprecated and will be removed in a future release. See '/help deprecated'
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I think deeply, FIIRST there is preprocessor, and THEN compiler. so it should be fine for preprocessor macros generating functions and/or parts of function. But modern compilers have preprocessing and compilation got together in one single step...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
MrAnderson (Intel) wrote:
On Windows, it is /debug:inline-debug-info, according to the documentation.
I am very sorry for misinformations, but I must say it is hard to google all ICC switches (from reliable sources).
Yes, "/debug:inline-debug-info" had the same effect on my build. Thank you for letting me know.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page