https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99215
--- Comment #2 from Nils Gladitz <nilsgladitz at gmail dot com> --- (In reply to Iain Sandoe from comment #1) > Can you identify specific key blockers to progress? > (I think the paper cited contained a number of desiderata, but it would be > good to start from the most important requirements). Thank you for the quick reply. As you and the paper have stated setting breakpoints so far seems to work fine for me. What stands out most for me is being unable to inspect parameters (which for the debugger don't seem to exist) and local variables (their names seem to be known but their values all show as "<optimized out>"). On second look this seems to be only half true as I seem to be able to inspect both local variables and parameters via the debugger visible "frame_ptr" variable. Not straightforward and names seem to be mangled but that might suffice to get started to some degree; won't work with gdb frontends though (which I have been using). I have no idea of how any of this is actually implemented but I am hoping this is just a matter of emitting debug information that tells gdb to look for members and parameters in the corresponding frame_ptr locations?
