An experiment in table driven code generation
SIGPLAN '82 Proceedings of the 1982 SIGPLAN symposium on Compiler construction
Writing efficient code
Performance tuning with instruction-level cost derived from call-stack sampling
ACM SIGPLAN Notices
The road not taken: Estimating path execution frequency statically
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
Accelerating multiple target drug screening on GPUs
Proceedings of the 9th International Conference on Computational Methods in Systems Biology
Catch me if you can: performance bug detection in the wild
Proceedings of the 2011 ACM international conference on Object oriented programming systems languages and applications
Proceedings of the 9th ACM Conference on Embedded Networked Sensor Systems
Proceedings of the 33rd ACM SIGPLAN conference on Programming Language Design and Implementation
Data mining MPSoC simulation traces to identify concurrent memory access patterns
Proceedings of the Conference on Design, Automation and Test in Europe
An online service-oriented performance profiling tool for cloud computing systems
Frontiers of Computer Science: Selected Publications from Chinese Universities
Improving the fault resilience of an H.264 decoder using static analysis methods
ACM Transactions on Embedded Computing Systems (TECS) - Special Section on ESTIMedia'10
Hi-index | 0.00 |
We extended the UNIX® system's profiler by gathering arcs in the call graph of a program. Here is it 20 years later and this profiler is still in daily use. Why is that? It's not because there aren't well-known areas for improvement.Large complex programs are composed of many small routines that implement abstractions for the routines that call them. To be useful, an execution profiler must attribute execution time in a way that is significant for the logical structure of a program as well as for its textual decomposition. This data must then be displayed to the user in a convenient and informative way. The gprof profiler accounts for the running time of called routines in the running time of the routines that call them. The design and use of this profiler is described.