[Bug target/111362] [14 Regression] '-fcompare-debug' failure (length) with -O -fno-tree-ch --param=max-completely-peel-times=0 -march=rv64iv

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

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jeff Law <law@gcc.gnu.org>:

https://gcc.gnu.org/g:50531b6d400945793a1d549e6ee941d989319d42

commit r14-9415-g50531b6d400945793a1d549e6ee941d989319d42
Author: jlaw <jeffreyalaw@gmail.com>
Date:   Sat Mar 9 19:27:32 2024 -0700

    [committed] [PR target/111362] Fix compare-debug issue with mode switching

    The issue here is the code we emit for mode-switching can change when -g is
    added to the command line.  This is caused by processing debug notes
occurring
    after a call which is the last real statement in a basic block.

    Without -g the CALL_INSN is literally the last insn in the block and the
loop
    exits.  If mode switching after the call is needed, it'll be handled as we
    process outgoing edges.

    With -g the loop iterates again and in the processing of the node the
backend
    signals that a mode switch is necessary.

    I pondered fixing this in the target, but the better fix is to ignore the
debug
    notes in the insn stream.

    I did a cursory review of some of the other compare-debug failures, but did
not
    immediately see others which would likely be fixed by this change.  Sigh.

    Anyway, bootstrapped and regression tested on x86.  Regression tested on
rv64
    as well.

            PR target/111362
    gcc/
            * mode-switching.cc (optimize_mode_switching): Only process
            NONDEBUG insns.

    gcc/testsuite

            * gcc.target/riscv/compare-debug-1.c: New test.
            * gcc.target/riscv/compare-debug-2.c: New test.