| View previous topic :: View next topic |
| Author |
Message |
donb
Joined: 20 Jul 2004 Posts: 82 Location: The Portland Group, Inc.
|
Posted: Wed Mar 27, 2013 10:03 am Post subject: |
|
|
OK. It looks like we have more work to do to reproduce your problem.
One way to get some of the Compiler Feedback information is to compile with -Minfo (as opposed to -Minfo=ccff) and capture the output in a file. Some of the same information that you get in the Compiler Feedback features of the profiler will just be printed to the standard output. There are various suboptions to -Minfo to control what the output contains; see the compiler's '-help' output for details.
Of course in this case you will need to correlate the compiler feedback to the source code and profile data manually, and feedback will be lackling the "optimization hints" found in the Compiler Feedback. Sorry for the inconvenience. |
|
| Back to top |
|
 |
jtull
Joined: 30 Jun 2004 Posts: 234
|
Posted: Tue May 21, 2013 3:34 pm Post subject: TPR 19242 is fixed in the 13.5 release. |
|
|
TPR 18242 - pgprof is not always able to generate CCFF information a PVF-built executable
Corrected how file path names are processed on Windows by pgprof
is corrected in the 13.5 release.
Thanks for the report.
dave |
|
| Back to top |
|
 |
|