public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/102954] [12 regression] gcc.dg/vect/pr33804.c XPASSes
Date: Wed, 27 Oct 2021 10:44:46 +0000	[thread overview]
Message-ID: <bug-102954-4-2bMRRx5FZi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102954-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
> It was likely the vect_worthwhile_without_simd_p changes where we might now
> vectorize this loop using (unaligned) 'int'.
>
> Can you confirm that?

Indeed.  I've also noticed that another regression was caused by the
same change:

XPASS: gcc.dg/vect/slp-multitypes-3.c -flto -ffat-lto-objects 
scan-tree-dump-times vect "vectorized 1 loops" 1
XPASS: gcc.dg/vect/slp-multitypes-3.c -flto -ffat-lto-objects 
scan-tree-dump-times vect "vectorizing stmts using SLP" 2
XPASS: gcc.dg/vect/slp-multitypes-3.c scan-tree-dump-times vect "vectorized 1
loops" 1
XPASS: gcc.dg/vect/slp-multitypes-3.c scan-tree-dump-times vect "vectorizing
stmts using SLP" 2

Again 64-bit SPARC.

  parent reply	other threads:[~2021-10-27 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 17:04 [Bug tree-optimization/102954] New: " ro at gcc dot gnu.org
2021-10-26 17:16 ` [Bug tree-optimization/102954] " ro at gcc dot gnu.org
2021-10-27  7:16 ` [Bug testsuite/102954] " rguenth at gcc dot gnu.org
2021-10-27 10:44 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2022-05-06  8:31 ` [Bug testsuite/102954] [12/13 " jakub at gcc dot gnu.org
2023-05-08 12:22 ` [Bug testsuite/102954] [12/13/14 " rguenth at gcc dot gnu.org
2024-02-28 15:17 ` ro at gcc dot gnu.org
2024-02-28 15:17 ` ro at gcc dot gnu.org
2024-05-22 11:42 ` [Bug testsuite/102954] [12/13/14/15 " ro 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-102954-4-2bMRRx5FZi@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).