SROA debug experience and dexter thoughts
The past weeks the efforts were focused around the Scalar Replacement of Aggregates pass. This is an early stage pass and thus the amount of debug info loss should be minimized cause it impacts the whole compiler a lot more.
Our contribution has been to systematically show that IR-level invariants on debug info are being respected by SROA/mem2reg.
The debugify pass with the newly implemented debugify-each option was the main tool used.
I made a report after ruining SROA on the amalgamated sqlite source. The results were a clear indication that SROA was doing it's job just fine and the little instructions without DebugLoc were produced from clang and it wasn't SROA/mem2reg's fault.
After applying the above clang patches the results are even better.
Comparing the results to dexter ones
Dexter scored SROA low.
As Greg (dexter's creator) mentions the dexter results don't have to indicate that there is some kind of bug
My standard disclaimer with all results from this tool is that a non-perfect debugging experience score is not necessarily indicative of something wrong, but should be looked at in conjunction with all the other factors such as what the pass is trying to achieve optimization-wise.
And such is the case with SROA.
A bug report has been filed explaining the problem.
Basically after running SROA/mem2reg the optimizations will at many cases result in weird stepping behavior in the debugger. This is normal since that's the whole point of passes like SROA and LICM: to reduce the instructions by optimizing aggregates and loops.
This is bad from the debug perspective and thus scores low on dexter.
Optimized vs unoptimized debugging
An optimizers job is to make the code execute faster on the given machine. This comes at the cost of modifying the code to a point that it no longer resembles the source material. Thus we rely on the descriptive power of the standard that is used to encode DI.
Passes that move code around or shorten the execution paths like SROA and LICM should go to great lengths to preserve the debug intrinsics that correspond the the name and value of the variables. It would be an unrealistic goal to try and keep the stepping behavior inside a debugger intact after running such passes.
Instead different optimization methods can be used when debugging is a high priority. Ones that don't move code around as much and of course result in longer execution times, but what they lose in speed they give back with a more robust debug experience.
SROA does a very good job preserving all the important Debug Information that it's given. On the other hand it significantly impacts the debug user experience but there is nothing that can be done about it as this is the nature of the transformation.