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 testsuite/103935] [12 regression] g++.dg/vect/slp-pr98855.cc fails after r12-6273
Date: Mon, 10 Jan 2022 10:43:59 +0000	[thread overview]
Message-ID: <bug-103935-4-NjlZbrADB5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103935-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Well, it was

// This used to work on { target x86_64-*-* i?86-*-* } but a fix in SLP
// discovery makes us trip over the threshold again.
// { dg-final { scan-tree-dump-times "not vectorized: vectorization is not prof
itable" 2 "slp1" { xfail *-*-* } } }

and it was xfailed, but you changed it to

// { dg-final { scan-tree-dump "not vectorized: vectorization is not profitable
" "slp1" } }
// { dg-final { scan-tree-dump-not "vectorizing stmts using SLP" "slp1" } }

no longer xfailed.  I suggest to re-add the { xfail *-*-* } to the
profitability
check.

  parent reply	other threads:[~2022-01-10 10:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 22:02 [Bug other/103935] New: " seurer at gcc dot gnu.org
2022-01-06 22:06 ` [Bug testsuite/103935] " pinskia at gcc dot gnu.org
2022-01-06 22:33 ` ubizjak at gmail dot com
2022-01-10 10:43 ` rguenth at gcc dot gnu.org [this message]
2022-01-10 11:05 ` ubizjak at gmail dot com
2022-01-10 11:14 ` rguenth at gcc dot gnu.org
2022-01-12 19:39 ` cvs-commit at gcc dot gnu.org
2022-01-12 19:47 ` ubizjak at gmail dot com

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-103935-4-NjlZbrADB5@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).