You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Omnitrace could have an option to do binary rewrite on object files, and an option to intercept a compiler invocation to rewrite the file after it was compiled similar to how ccache or distcc work.
I'm guessing the linker will not have problems with linking instrumented functions.
This would allow for a workflow where only changed files have to be re-instrumented, potentially significantly cutting down on the time it takes to get a new trace after tweaking an application.
With projects in cmake using an option like this would be as easy as setting CMAKE_COMPILER_LAUNCHER.
The text was updated successfully, but these errors were encountered:
An alternative might be to instead just provide a CMake target which adds -finstrument-functions flags to the target and provides a library with the instrumentation functions? The trade-off here is the decreased control over which functions get instrumented.
Omnitrace could have an option to do binary rewrite on object files, and an option to intercept a compiler invocation to rewrite the file after it was compiled similar to how
ccache
ordistcc
work.I'm guessing the linker will not have problems with linking instrumented functions.
This would allow for a workflow where only changed files have to be re-instrumented, potentially significantly cutting down on the time it takes to get a new trace after tweaking an application.
With projects in cmake using an option like this would be as easy as setting
CMAKE_COMPILER_LAUNCHER
.The text was updated successfully, but these errors were encountered: