public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/111125] [14 Regression] tree-ssa.exp and vect.exp failures after commit r14-3281-g99b5921bfc8f91
Date: Thu, 24 Aug 2023 08:44:31 +0000	[thread overview]
Message-ID: <bug-111125-4-9zArHIXYu2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111125-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
For gcc.dg/vect/bb-slp-29.c we are now vectorizing

#pragma GCC novector
  for (i = 0; i < N/2; i++)
    {
      if (dst[i] != A * src[i] + B * src[i+1])
        abort ();
    }

in particular the multiplication and the addition (but not the load which
had predictive commoning applied).  When cost modeling is enabled this
vectorization is not deemed profitable (but the vect testsuite runs with
-fno-vect-cost-model).

I wonder if we want to excempt basic blocks within loops marked with novector
from BB vectorization.

  parent reply	other threads:[~2023-08-24  8:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  2:05 [Bug middle-end/111125] New: tree-ssa.exp and vect.exp failures after commit 99b5921bfc8f thiago.bauermann at linaro dot org
2023-08-24  7:41 ` [Bug middle-end/111125] [14 Regression] tree-ssa.exp and vect.exp failures after commit r14-3281-g99b5921bfc8f91 rguenth at gcc dot gnu.org
2023-08-24  8:15 ` rguenth at gcc dot gnu.org
2023-08-24  8:44 ` rguenth at gcc dot gnu.org [this message]
2023-08-24  8:54 ` rguenth at gcc dot gnu.org
2023-08-24  8:59 ` cvs-commit at gcc dot gnu.org
2023-08-24  9:36 ` cvs-commit at gcc dot gnu.org
2023-08-24 11:03 ` cvs-commit at gcc dot gnu.org
2023-08-24 11:03 ` rguenth at gcc dot gnu.org
2023-08-24 15:38 ` thiago.bauermann at linaro dot 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-111125-4-9zArHIXYu2@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).