New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could you please help with compile under profiler support like gprof #3659
Comments
|
It look like require But may be meson contain keyword argument to compile with profiling instead do it by hand? |
|
Hmmm, apparently we don't have an option for that. It would be a useful addition, so patches are welcome as usual? In the mean time you might consider using some other profiler, such as the one integrated in Valgrind. |
|
@jpakkane Valgrind is well working but some very real-time application may degradate performance. I does know about gpref but belive that it less affect my own application performance. |
|
Yes. that would be a welcome feature instead of crawling the web towards that issue |
|
+1 for this feature. |
|
@jpakkane @eli-schwartz you can assign this to me. Should profiling be added as an additional value for the 'buildtype' core option? |
|
Is it a build type? The current ones map to various debug/optimization settings. This seems more in the same genre as sanitizers, fanalyzer, and so on, so I'd expect it to be a |
|
I prefer |
In the gcc docs, it's listed under the Instrumentation heading. I'll start by adding it as a 'b_...' option. One sticking point.. Besides
So do we need a |
|
One option, but it accepts 3 choices (similar to how optimization accepts several choices depending on what kind of optimization you want). |
|
Do we actually need to add an option for 'prof'? I can't even find that program in Arch Linux or Debian. |
I create some application and want understand profile information over gprof.
Tight now I add
As result I receive gmon.out but gprof does not provide any result. Do u know where problem may bey exists?
The text was updated successfully, but these errors were encountered: