search for: _tracking_

For -Rpass, and other related uses, I am looking at enabling column info by default. David pointed me at PR 14106, which seems to be the original motivation for introducing -gcolumn-info. However, I am finding no differences when using it on this test. I've tried building with/without -gcolumn-info and found almost no difference in compile time (+0.4%): $ /usr/bin/time clang -w -fno-builtin

...gt; Or it can affect single-stepping, which might stop at the next > “is-statement” entry, even if the line hasn’t changed. “How come I have to > hit Step 4 times to get it to go to the next line?” > > > > For –Rpass and related uses, it might be useful to distinguish between > _tracking_ column numbers and _emitting_ column numbers. IIUC –Rpass wants > column info tracked during compilation so it can show the things it wants to > show with maximum relevance. Whether those column numbers actually make it > into the .debug_line section is a different story. > > --paulr...

...gdb testsuite to see whether that's a real problem. If that's a problem, it should show there (since GCC does not emit column info in dwarf, AFAIR). In any case, that would be a debugger issue. Not compiler. > For –Rpass and related uses, it might be useful to distinguish between > _tracking_ column numbers and _emitting_ column numbers. IIUC –Rpass wants > column info tracked during compilation so it can show the things it wants to > show with maximum relevance. Whether those column numbers actually make it > into the .debug_line section is a different story. That's alrea...