[Bug target/104440] nvptx: FAIL: gcc.c-torture/execute/pr53465.c execution test

["cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104440

--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom de Vries <vries@gcc.gnu.org>:

https://gcc.gnu.org/g:02aedc6f269b5e3c1f354edcf5b84d27b0a15946

commit r12-7312-g02aedc6f269b5e3c1f354edcf5b84d27b0a15946
Author: Tom de Vries <tdevries@suse.de>
Date:   Wed Feb 16 17:09:11 2022 +0100

    [nvptx] Initialize ptx regs

    With nvptx target, driver version 510.47.03 and board GT 1030 I, we run
into:
    ...
    FAIL: gcc.c-torture/execute/pr53465.c -O1 execution test
    FAIL: gcc.c-torture/execute/pr53465.c -O2 execution test
    FAIL: gcc.c-torture/execute/pr53465.c -O3 -g execution test
    ...
    while the test-cases pass with nvptx-none-run -O0.

    The problem is that the generated ptx contains a read from an uninitialized
    ptx register, and the driver JIT doesn't handle this well.

    For -O2 and -O3, we can get rid of the FAIL using --param
    logical-op-non-short-circuit=0.  But not for -O1.

    At -O1, the test-case minimizes to:
    ...
    void __attribute__((noinline, noclone))
    foo (int y) {
      int c;
      for (int i = 0; i < y; i++)
        {
          int d = i + 1;
          if (i && d <= c)
            __builtin_abort ();
          c = d;
        }
    }

    int main () {
      foo (2); return 0;
    }
    ...

    Note that the test-case does not contain an uninitialized use.  In the
first
    iteration, i is 0 and consequently c is not read.  In the second iteration,
c
    is read, but by that time it's already initialized by 'c = d' from the
first
    iteration.

    AFAICT the problem is introduced as follows: the conditional use of c in
the
    loop body is translated into an unconditional use of c in the loop header:
    ...
      # c_1 = PHI <c_4(D)(2), c_9(6)>
    ...
    which forwprop1 propagates the 'c_9 = d_7' assignment into:
    ...
      # c_1 = PHI <c_4(D)(2), d_7(6)>
    ...
    which ends up being translated by expand into an unconditional:
    ...
    (insn 13 12 0 (set (reg/v:SI 22 [ c ])
            (reg/v:SI 23 [ d ])) -1
         (nil))
    ...
    at the start of the loop body, creating an uninitialized read of d on the
    path from loop entry.

    By disabling coalesce_ssa_name, we get the more usual copies on the
incoming
    edges.  The copy on the loop entry path still does an uninitialized read,
but
    that one's now initialized by init-regs.  The test-case passes, also when
    disabling init-regs, so it's possible that the JIT driver doesn't object to
    this type of uninitialized read.

    Now that we characterized the problem to some degree, we need to fix this,
    because either:
    - we're violating an undocumented ptx invariant, and this is a compiler
bug,
      or
    - this is is a driver JIT bug and we need to work around it.

    There are essentially two strategies to address this:
    - stop the compiler from creating uninitialized reads
    - patch up uninitialized reads using additional initialization

    The former will probably involve:
    - making some optimizations more conservative in the presence of
      uninitialized reads, and
    - disabling some other optimizations (where making them more conservative
is
      not possible, or cannot easily be achieved).
    This will probably will have a cost penalty for code that does not suffer
from
    the original problem.

    The latter has the problem that it may paper over uninitialized reads
    in the source code, or indeed over ones that were incorrectly introduced
    by the compiler.  But it has the advantage that it allows for the problem
to
    be addressed at a single location.

    There's an existing pass, init-regs, which implements a form of the latter,
    but it doesn't work for this example because it only inserts additional
    initialization for uses that have not a single reaching definition.

    Fix this by adding initialization of uninitialized ptx regs in reorg.

    Control the new functionality using -minit-regs=<0|1|2|3>, meaning:
    - 0: disabled.
    - 1: add initialization of all regs at the entry bb
    - 2: add initialization of uninitialized regs at the entry bb
    - 3: add initialization of uninitialized regs close to the use
    and defaulting to 3.

    Tested on nvptx.

    gcc/ChangeLog:

    2022-02-17  Tom de Vries  <tdevries@suse.de>

            PR target/104440
            * config/nvptx/nvptx.cc (workaround_uninit_method_1)
            (workaround_uninit_method_2, workaround_uninit_method_3)
            (workaround_uninit): New function.
            (nvptx_reorg): Use workaround_uninit.
            * config/nvptx/nvptx.opt (minit-regs): New option.