[Bug testsuite/113502] gcc.target/aarch64/vect-early-break-cbranch.c and gcc.target/aarch64/sve/vect-early-break-cbranch.c testcase are too sensitive

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

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

--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tamar Christina <tnfchris@gcc.gnu.org>:

https://gcc.gnu.org/g:f7935beef7b02fbba0adf33fb2ba5c0a27d7e9ff

commit r14-8662-gf7935beef7b02fbba0adf33fb2ba5c0a27d7e9ff
Author: Tamar Christina <tamar.christina@arm.com>
Date:   Wed Jan 31 14:52:59 2024 +0000

    AArch64: relax cbranch tests to accepted inverted branches [PR113502]

    Recently something in the midend had started inverting the branches by
inverting
    the condition and the branches.

    While this is fine, it makes it hard to actually test.  In RTL I disable
    scheduling and BB reordering to prevent this.  But in GIMPLE there seems to
be
    nothing I can do.  __builtin_expect seems to have no impact on the change
since
    I suspect this is happening during expand where conditions can be flipped
    regardless of probability during compare_and_branch.

    Since the mid-end has plenty of correctness tests, this weakens the backend
    tests to just check that a correct looking sequence is emitted.

    gcc/testsuite/ChangeLog:

            PR testsuite/113502
            * gcc.target/aarch64/sve/vect-early-break-cbranch.c: Ignore exact
branch.
            * gcc.target/aarch64/vect-early-break-cbranch.c: Likewise.