public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/109705] New: [14 regression] gcc.dg/vect/pr25413a.c fails after r14-333-g6d4b59a9356ac4
Date: Wed, 03 May 2023 00:05:21 +0000 [thread overview]
Message-ID: <bug-109705-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109705
Bug ID: 109705
Summary: [14 regression] gcc.dg/vect/pr25413a.c fails after
r14-333-g6d4b59a9356ac4
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:6d4b59a9356ac4df7f4ae370495dc3366d0daa55, r14-333-g6d4b59a9356ac4
make -k check-gcc RUNTESTFLAGS="vect.exp=gcc.dg/vect/pr25413a.c"
FAIL: gcc.dg/vect/pr25413a.c scan-tree-dump-times vect "vectorized 2 loops" 1
FAIL: gcc.dg/vect/pr25413a.c -flto -ffat-lto-objects scan-tree-dump-times vect
"vectorized 2 loops" 1
# of expected passes 4
# of unexpected failures 2
commit 6d4b59a9356ac4df7f4ae370495dc3366d0daa55 (HEAD, refs/bisect/bad)
Author: Richard Biener <rguenther@suse.de>
Date: Wed Jan 18 10:59:52 2023 +0100
Add emulated scatter capability to the vectorizer
* gcc.dg/vect/pr25413a.c: Un-XFAIL everywhere.
This fails on power 8 and 9 LE but is OK on BE and on power 10.
Perhaps there is some LE optimization missing previous to power 10?
next reply other threads:[~2023-05-03 0:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 0:05 seurer at gcc dot gnu.org [this message]
2023-05-03 6:49 ` [Bug testsuite/109705] " rguenth at gcc dot gnu.org
2023-05-03 8:19 ` segher at gcc dot gnu.org
2023-05-03 9:13 ` rguenther at suse dot de
2024-01-12 10:45 ` rguenth at gcc dot gnu.org
2024-01-15 13:50 ` rguenth at gcc dot gnu.org
2024-01-16 2:56 ` cvs-commit at gcc dot gnu.org
2024-01-19 15:44 ` bergner at gcc dot gnu.org
2024-01-22 3:14 ` linkw at gcc dot gnu.org
2024-01-24 7:44 ` pinskia at gcc dot gnu.org
2024-01-24 17:37 ` pinskia at gcc dot gnu.org
2024-01-24 17:40 ` pinskia at gcc dot gnu.org
2024-01-24 18:20 ` pinskia at gcc dot gnu.org
2024-01-24 18:22 ` cvs-commit at gcc dot gnu.org
2024-01-25 21:57 ` pinskia at gcc dot gnu.org
2024-01-26 5:06 ` pinskia at gcc dot gnu.org
2024-01-26 7:35 ` cvs-commit at gcc dot gnu.org
2024-01-26 7:35 ` pinskia at gcc dot gnu.org
2024-01-26 21:28 ` seurer at gcc dot gnu.org
2024-01-26 21:35 ` pinskia at gcc dot gnu.org
2024-01-26 21:36 ` pinskia at gcc dot gnu.org
2024-01-26 22:38 ` pinskia at gcc dot gnu.org
2024-01-26 22:43 ` pinskia at gcc dot gnu.org
2024-01-29 2:36 ` cvs-commit at gcc dot gnu.org
2024-01-29 3:29 ` pinskia 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-109705-4@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).