Point out the correct line number in stack traces

Sometimes the line number in a stack trace could be wrong,
for example for this code:

    t() ->
        Res = id(x), %<== Wrong line number.
        Res + 1.

    id(I) -> I.

The line number pointed out in the stack trace would be the
line before the line where the exception occurred.

The reason is the way the increment instruction instruction
is implemented:

    OpCase(i_increment_rWtd):
    {
      increment_reg_val = r(0);
    }
    I -= 1;
    goto increment__execute;

    OpCase(i_increment_xWtd):
    {
      increment_reg_val = xb(I[1]);
    }
    goto increment__execute;

    increment__execute:
    /* Common code for increment */
    .
    .
    .

(The implementation in OTP 20 is similar, but hand-coded directly
in beam_emu.c instead of generated.)

The instruction i_increment_rWtd decrements the instruction pointer (I)
before jumping to the common code. That means that I points *before*
the 'increment' instruction. If there is a 'line' instruction directly
before the 'increment' instruction (as there is in this example), the
instruction pointer will point before that line. Thus the previous line
will be picked up instead.

To eliminate this bug, we must never decrement the instruction pointer.
Instead, we can increment the other (longer) instructions in the
same group of combined instructions:

    OpCase(i_increment_rWtd):
    {
      increment_reg_val = r(0);
    }
    goto increment__execute;

    OpCase(i_increment_xWtd):
    {
      increment_reg_val = xb(I[1]);
    }
    I += 1;
    goto increment__execute;

    increment__execute:
    /* Common code for increment */
    .
    .
    .

Also fix a bug that was only a potential bug when ddaed7774eb0a
introduced relative jumps, but is now a real bug. See the added
comment for SET_I_REL() in macros.tab.

0 files changed, 0 insertions, 0 deletions