search for: prefigured

...statement would have to be included with all those statement. I felt the lack of something like this severely when digging out dozens of compiler bugs on Microsoft's Itanium compiler, over a decade ago. That processor "naturally" mixed instructions from many source statements, which prefigured this kind of problem. I'm reasonably happy for debugging at high optimisation levels to be primarily done with a disassembly listing rather than source code, provided I can get some idea of which instructions come from which source statements, and which variables are being accessed. The absenc...

On 7 June 2013 13:53, Dallman, John <john.dallman at siemens.com> wrote: > It needs to be possible to debug code at any optimisation level. > Yes, I agree. But after O1, sequential execution is a big impediment for optimizations, and keeping the debug information valid after so many transformations might pose a big penalty on the passes (time & memory). That was the whole idea

I'm not a LLVM or Clang developer, but I do spend a lot of time teasing software into working with the highest possible optimisation levels where it still works correctly. These guidelines are pretty good, but there are a few details worth considering. It needs to be possible to debug code at any optimisation level. It's acceptable for that to be harder at high optimisation levels, but