public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113167] [14 Regression] gcc.dg/tree-ssa/gen-vect-26.c started failing many targets after recent change
Date: Fri, 29 Dec 2023 04:50:21 +0000	[thread overview]
Message-ID: <bug-113167-4-U5IyrEeyNc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113167-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:200531d5b9fb99eca2b0d6b8d1e42d176413225f

commit r14-6861-g200531d5b9fb99eca2b0d6b8d1e42d176413225f
Author: Andrew Pinski <quic_apinski@quicinc.com>
Date:   Thu Dec 28 20:26:01 2023 -0800

    Fix gen-vect-26.c testcase after loops with multiple exits [PR113167]

    This fixes the gcc.dg/tree-ssa/gen-vect-26.c testcase by adding
    `#pragma GCC novector` in front of the loop that is doing the checking
    of the result. We only want to test the first loop to see if it can be
    vectorize.

    Committed as obvious after testing on x86_64-linux-gnu with -m32.

    gcc/testsuite/ChangeLog:

            PR testsuite/113167
            * gcc.dg/tree-ssa/gen-vect-26.c: Mark the test/check loop
            as novector.

    Signed-off-by: Andrew Pinski <quic_apinski@quicinc.com>

  parent reply	other threads:[~2023-12-29  4:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-29  3:55 [Bug tree-optimization/113167] New: " law at gcc dot gnu.org
2023-12-29  4:22 ` [Bug testsuite/113167] " pinskia at gcc dot gnu.org
2023-12-29  4:24 ` pinskia at gcc dot gnu.org
2023-12-29  4:40 ` pinskia at gcc dot gnu.org
2023-12-29  4:50 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-29  4:51 ` pinskia at gcc dot gnu.org
2023-12-29  8:40 ` tnfchris at gcc dot gnu.org
2023-12-29 16:29 ` law at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-113167-4-U5IyrEeyNc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).