Forum Discussion

newsgroups's avatar
newsgroups
Occasional Contributor
11 years ago
Solved

Uninstrumented routines, Duplicate code, C++ Builder XE4

When I run a Performance profiler on my VCL GUI application, the Uninstrumented Routines dialog reports that all of my forms that derive from base forms contain Duplicated Code. How can I find ...
  • aqAnt's avatar
    aqAnt
    11 years ago


    Hi All,



    We are constantly working on improving the code instrumentation. However, AQtime's ability to instrument a certain routine heavily depends on how the compiler generates the routine's code. So, the generated binary code analysis clarifies why it cannot be instrumented. Note: AQtime provides the Disassembler panel to analyze the binary code.



    The Profiling Duplicated Code article contains an example of how to affect the generated code to instrument it. In general, we suggest that you adjust optimization settings of your compiler to determine how it affects the Uninstrumented Routines dialog's list.


newsgroups's avatar
newsgroups
Occasional Contributor
11 years ago
To update anybody who may be reading this thread, Jay noted that I was profiling a C++ Builder XE4 GUI application compiled for 64-bit. He suggested I try building it as 32-bit and see if that made a difference.



It did. Not only did the warnings about duplicate code go away, but AQtime was able to open my executable instantly; the 64-bit build takes upwards of ten minutes to analyze upon opening.