hy9be / micro-profiler

Automatically exported from code.google.com/p/micro-profiler
0 stars 0 forks source link

Multiple instances of all calling functions/instances while profiling using intel compiler #21

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Added micro-profiler in MSVS 2010 professional edition. Till this it is 
profiling as expected. 
2.Than toggle compiler to Intel Parallel Studio C++ professional compiler.
3.Code execution for profiling.

What is the expected output? What do you see instead?
Ans.The profiler should profile of each functions and shows its individuals 
timings. But it shows multiple instances of functions and some of them are with 
0 Second execution time which is practically incorrect, as mentioned in 
attached file of both the compiler.

What version of the product are you using? On what operating system?
Ans.I have embedded "Intel Compiler XE 2015 professional edition for C++" on 
Windows 7 64-bit OS and Intel core i5 2400 quadcore CPU.

Please provide any additional information below.
I covered almost.

Original issue reported on code.google.com by bhattite...@gmail.com on 17 Oct 2014 at 1:21

Attachments:

GoogleCodeExporter commented 9 years ago
You may have such output in case 'DetectionAlgorithm9' is overloaded. Is it?

Is this function a static/inline with reccurence declared in header and used 
across several .cpp files?

If not, this may be a nuance of Intel compiler. Anyway, provided that both 
enters and exits are properly tracked, this seems to look like several 
instances of the same method.

Can you try 'minimize size' optimization to see, if these call are merged into 
one?

Original comment by artem.ge...@gmail.com on 17 Oct 2014 at 2:31

GoogleCodeExporter commented 9 years ago
The 'DetectionAlgorithm9' function is not overloaded and its a single function

No. Function is declared as extern in header file, only once. Its not static or 
inline, not even used several .cpp files.

I have tried with 'minimize size' optimization, but its behavior is same as 
previous. It only works as expected with 'No Optimization' setting in Intel C++ 
Compiler.

Original comment by bhattite...@gmail.com on 20 Oct 2014 at 8:52