On Thu, Apr 25, 2019 at 12:04:24PM +0200, Richard Biener wrote:
> >Bootstrapped/regtested on x86_64-linux and i686-linux, ok for trunk?
>
> So if you put a breakpoint on the for line is the behavior after the patch
> now the same as before stmt frontiers if you do 'continue' repeatedly?
The cc1 behavior before the patch with -g -O2 -gno-statement-frontiers
is the same as patched cc1 with -g -O2 in both the
b test; r; n; n; n; n; n; n
behavior as well as in
// line number depending on the test - -1, -2, -3
b {5,6,8}; r; c
The latter in the for and while loops it breaks just once and continue runs
till end of program; I think the behavior of gdb here is that only the very
first breakpoint on that particular line counts, not the others.
For do while loop where the break is on the condition line, both unpatched
-gno-statement-frontiers and patched without that break on every iteration
on the condition.
Now, if the for statement has the condition and increment on separate lines,
then again both unpatched -gno-statement-frontiers and patched without
if the breakpoint is put on the condition or increment lines rather than the
first one will break on every iteration.
Jakub
