How could we profile a c program in order to obtain detailed information related to its executed instructions (Dynamic Instructions)? I'm looking for a tool with which I can use it to obtain information per dynamic instruction, for example
The 1st Instruction is executed 10 times
The 2nd Instruction is executed 5 times
The 3rd Instruction is executed 7 times and so on.
Moreover, taking into account arithmetic instructions, is it possible to determine the results that those instructions produce for each time they are being executed (the partial results produced by a dynamic instruction at an arbitrary clock cycle)?
By doing so, we can state that instruction 1 is going to execute 10 times and the results it produces are the same as across these 10 times. Therefore, we can ignore 9 dynamic instructions of instruction 1, and only consider one instance.
I Still haven't found what I'm looking for!
Hello Hussein,
Many good C/C++ compilers already have an inbuilt tracer/debugger with instruction stepping, etc, for that. I know that Microsoft Visual C/C++ certainly has it because I have used it in the past. It is a rather difficult matter to make sense of most but the simplest programs because of branching and multithreading. Therefore, the usefulness of a tool is as good as you make sense of its outputs.
Regards,
Dear Hussein,
I am also not aware of any tool that can count instructions; however, if you use GDB, you can write a simple python script that does a step-by-step execution of the code, and records and counts the number of times the instructions are being executed, in a simple dictionary. I think that, however, any tracer that you might use will make your software very slow by some orders of magnitude.
If you just want to count certain instructions, you can write a simple python script in GDB that inspects the memory and adds a conditional breakpoint that increments a variable and continues execution. Finally, you might want to have a look at radare2 to debug at low-level and look at, in particular, its macro capabilities.
Regards,
Tiago
Profiling is achieved by instrumenting either the program source code or its binary executable form using a tool called a profiler (or code profiler). Profilers may use a number of different techniques, such as event-based, statistical, instrumented, and simulation methods.
Iostat is a tool used to monitor system I/O by reading files in the /proc filesystem and comparing the time the devices are active to their average transfer rates. It is available as part of the sysstat package..
Profiling is the practice of attempting to understand a person or group based on general characteristics or on past behaviors. An example of profiling is a situation where a person is pulled aside for extra screening at an airport because of their race.
code Profiling and Performance Tools for Visual Studio
- AMD CodeXL. ...
- JetBrains dotTrace. ...
- RedGate ANTS. ...
- Telerik JustTrace. ...
- Visual Studio Performance and Diagnostics Hub. ...
- More Performance Tools. ...
- Better, Stronger, Faster.
Dear Hussein,
probably you can try the "GooglePerformance tools" .
https://blog.csdn.net/zmyer/article/details/20394511?utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromMachineLearnPai2%7Edefault-1.control&depth_1-utm_source=distribute.pc_relevant.none-task-blog-2%7Edefault%7EBlogCommendFromMachineLearnPai2%7Edefault-1.control
here's the blog in the CSDN.
click to see this article
http://rg1-teaching.mpi-inf.mpg.de/advancedc-ws08/script/lecture06.pdf
Hussien Al-haj Ahmad , You can use GCOV.
gcov is a test coverage program. Use it in concert with GCC to analyze your programs to help create more efficient, faster running code and to discover untested parts of your program. You can use gcov as a profiling tool to help discover where your optimization efforts will best affect your code.
https://man7.org/linux/man-pages/man1/gcov.1.html
- Badges
- Science topic
- Similar topics
- Computer Science
- Program