search for: locstat

...e’ and ‘-dwarf-version’ LLVM code-generation flags, since not all debuggers used in the community consume this DWARF information. Location coverage improvement The important criteria in debugging-optimized-code is whether the compiler has location information for variables and parameters. We use ‘locstats’ utility from elfutils [5] package to guide us in improving overall location coverage in final executable. For each non-artificial variable or formal parameter - or Debugging Information Entry in DWARF - ‘locstats’ computes what percentage from the code section bytes where the variable is in scope...

...you on this, we are open for suggestion. I will ask my colleagues on this project to respond too. > > Location coverage improvement > The important criteria in debugging-optimized-code is whether the compiler has location information for variables and parameters. We use ‘locstats’ utility from elfutils [5] package to guide us in improving overall location coverage in final executable. For each non-artificial variable or formal parameter - or Debugging Information Entry in DWARF - ‘locstats’ computes what percentage from the code section bytes where the variable is in scope...

Hi llvm-dev@ LNT produces statistics and graphs (such as [0]) of debuginfo metrics, such as number of source variables with locations. It looks like these haven't run [1] since the move from svn to git -- are there any plans to get these running again? I find it highly useful to identify what commits have affected variable locations and how significant an affect. [0]

...leagues on this project to respond too. > > > > > > Location coverage improvement > > The important criteria in debugging-optimized-code is whether the > compiler has location information for variables and parameters. We use > ‘locstats’ utility from elfutils [5] package to guide us in improving > overall location coverage in final executable. For each non-artificial > variable or formal parameter - or Debugging Information Entry in DWARF - > ‘locstats’ computes what percentage from the code section bytes whe...

...n referencing" implementation I've been doing, see this RFC [0, 1] for background. It's now at the point where I'd call it "done" (as far as software ever is), and so it's a good time to look at what results it produces. And here are the scores-on-the-doors using llvm-locstats, on clang-3.4 RelWithDebInfo first in "normal" mode and then with -Xclang -fexperimental-debug-variable-locations. "normal": ================================================= cov% samples percentage(~) -------------------------------------------------...

...> implementation I've been doing, see this RFC [0, 1] for background. It's now at > the point where I'd call it "done" (as far as software ever is), and so it's a > good time to look at what results it produces. And here are the > scores-on-the-doors using llvm-locstats, on clang-3.4 RelWithDebInfo first in > "normal" mode and then with -Xclang -fexperimental-debug-variable-locations. > "normal": > > ================================================= > cov% samples percentage(~) > ---------------------...