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/106879] New: [13 regression] new test case gcc.dg/vect/bb-slp-layout-19.c fails
Date: Wed, 07 Sep 2022 17:36:28 +0000 [thread overview]
Message-ID: <bug-106879-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106879
Bug ID: 106879
Summary: [13 regression] new test case
gcc.dg/vect/bb-slp-layout-19.c fails
Product: gcc
Version: 13.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:eab511df13ca6abb24c3c2abb0f420a89c91e310, r13-2377-geab511df13ca6a
make -k check-gcc RUNTESTFLAGS="vect.exp=gcc.dg/vect/bb-slp-layout-19.c"
FAIL: gcc.dg/vect/bb-slp-layout-19.c -flto -ffat-lto-objects
scan-tree-dump-times slp1 "add new stmt: [^\\n\\r]* = VEC_PERM_EXPR" 3
FAIL: gcc.dg/vect/bb-slp-layout-19.c -flto -ffat-lto-objects
scan-tree-dump-times slp1 "add new stmt: [^\\n\\r]* = VEC_PERM_EXPR" 3
FAIL: gcc.dg/vect/bb-slp-layout-19.c scan-tree-dump-times slp1 "add new stmt:
[^\\n\\r]* = VEC_PERM_EXPR" 3
FAIL: gcc.dg/vect/bb-slp-layout-19.c scan-tree-dump-times slp1 "add new stmt:
[^\\n\\r]* = VEC_PERM_EXPR" 3
This is on powerpc64 BE. It works fine on LE.
This one fails too.
FAIL: gcc.dg/vect/bb-slp-layout-20.c -flto -ffat-lto-objects
scan-tree-dump-times slp1 "add new stmt: [^\\n\\r]* = VEC_PERM_EXPR" 3
FAIL: gcc.dg/vect/bb-slp-layout-20.c -flto -ffat-lto-objects
scan-tree-dump-times slp1 "add new stmt: [^\\n\\r]* = VEC_PERM_EXPR" 3
FAIL: gcc.dg/vect/bb-slp-layout-20.c scan-tree-dump-times slp1 "add new stmt:
[^\\n\\r]* = VEC_PERM_EXPR" 3
FAIL: gcc.dg/vect/bb-slp-layout-20.c scan-tree-dump-times slp1 "add new stmt:
[^\\n\\r]* = VEC_PERM_EXPR" 3
ESC[33mcommit eab511df13ca6abb24c3c2abb0f420a89c91e310ESC[m
Author: Richard Sandiford <richard.sandiford@arm.com>
Date: Fri Sep 2 14:00:14 2022 +0100
vect: Ensure SLP nodes don't end up in multiple BB partitions [PR106787]
next reply other threads:[~2022-09-07 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 17:36 seurer at gcc dot gnu.org [this message]
2022-09-08 9:35 ` [Bug testsuite/106879] " rguenth at gcc dot gnu.org
2022-10-21 2:59 ` pinskia at gcc dot gnu.org
2023-02-21 13:58 ` rguenth at gcc dot gnu.org
2023-02-21 16:16 ` seurer at gcc dot gnu.org
2023-03-27 14:05 ` rguenth at gcc dot gnu.org
2023-04-18 7:23 ` [Bug testsuite/106879] [13/14 " guojiufu at gcc dot gnu.org
2023-04-20 3:19 ` cvs-commit at gcc dot gnu.org
2023-04-26 6:56 ` rguenth at gcc dot gnu.org
2023-07-27 9:23 ` rguenth at gcc dot gnu.org
2024-01-12 10:01 ` [Bug testsuite/106879] [13 " rguenth at gcc dot gnu.org
2024-01-14 1:51 ` cvs-commit at gcc dot gnu.org
2024-01-14 1:52 ` guojiufu 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-106879-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).